vtex-io-auth-and-policies

Define authorization and policy boundaries for VTEX IO app manifests.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/exilonX/ap2 --skill vtex-io-auth-and-policies-exilonx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vtex-io-auth-and-policies
Source: https://github.com/exilonX/ap2/tree/main/.agents/skills/vtex-io-auth-and-policies
Command: npx skills add https://github.com/exilonX/ap2 --skill vtex-io-auth-and-policies-exilonx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents VTEX IO apps from failing authorization at runtime by guiding you to declare the exact permissions and access boundaries needed for integrations, protected routes, and external calls.

Core Features & Use Cases

  • Permission mapping for integrations: Ensures every external host, capability, and VTEX resource the app consumes is covered by the correct manifest policy type.
  • Least-privilege outbound access: Helps scope outbound-access rules narrowly by host and path to reduce risk and review complexity.
  • Server-side route enforcement alignment: Clarifies how route/resource-based policies define authorization boundaries so consumers do not mistakenly assume behavior is client-validated.
  • Decision rules for policy types: Guides when to use License Manager policies, app policies, outbound-access, and resource-based route policies using the right principal/VRN patterns.

Quick Start

Apply this Skill when reviewing or creating a VTEX IO manifest permissions change, so you can verify the policy type, scope, and server-side enforcement are consistent with the behavior being enabled.

Frequently Asked Questions about vtex-io-auth-and-policies

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure VTEX IO manifest policies for least-privilege outbound access?

To enforce least-privilege outbound access in VTEX IO, scope outbound-access rules narrowly by host and path within the manifest.json file, reducing risk and review complexity for external HTTP calls.

What is the difference between License Manager policies and app policies in VTEX IO?

License Manager policies and app policies in VTEX IO serve different authorization boundaries; selecting the correct policy type ensures server-side route enforcement and resource protection align with the actual integration behavior.

Why does my VTEX IO app fail authorization at runtime despite having manifest policies declared?

VTEX IO apps fail authorization at runtime when declared manifest permissions do not match the actual integrations and protected behavior required, meaning every protected integration needs an explicit supporting policy declared in manifest.json.

When do I need outbound-access rules in my VTEX IO manifest.json?

You need outbound-access rules in your VTEX IO manifest.json when your app makes external HTTP calls, ensuring the app has explicit permission to communicate with those specific external hosts and paths during runtime.

Can I use client-side validation instead of route policies for VTEX IO protected routes?

No, VTEX IO route and resource-based policies define server-side authorization boundaries, ensuring protected routes are enforced securely and consumers do not mistakenly assume the behavior is validated on the client.