List all CMS templates
AI agents call vtex_list_cms_templates to retrieve information from MCP VTEX Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns CMS template data without altering state, executing code, or triggering side effects. It is a straightforward read-only operation that lists existing templates. The VTEX server manages e-commerce operations including sensitive catalog and customer data, but listing CMS templates is a non-destructive information retrieval action with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name is 'vtex_list_cms_templates' and description states 'List all CMS templates' — a retrieval operation with no modification, deletion, execution, or financial impact.
Attacks that exploit this kind of access
List all CMS templates. It is categorised as a Read tool in the MCP VTEX Server MCP Server, which means it retrieves data without modifying state.
Register the MCP VTEX Server MCP server in PolicyLayer and add a rule for vtex_list_cms_templates: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches MCP VTEX Server. Nothing to install.
vtex_list_cms_templates is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the vtex_list_cms_templates rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for vtex_list_cms_templates. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
vtex_list_cms_templates is provided by the MCP VTEX Server MCP server (leosepulveda/mcp-vtex). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →