Get order form (cart) details by ID
AI agents call vtex_get_orderform 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 retrieves cart/order form information by ID. It queries existing data without creating, modifying, deleting, or executing any operations. The operation has no side effects and poses minimal risk, as it only exposes data the user should already have authorization to view. Classification as Read is appropriate.
From the tool's definition Tool name 'vtex_get_orderform' and description 'Get order form (cart) details by ID' indicate a retrieval operation with no side effects. The verb 'Get' and the action of retrieving existing data by ID are characteristic of Read operations.
Attacks that exploit this kind of access
Get order form (cart) details by ID. 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_get_orderform: 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_get_orderform 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_get_orderform 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_get_orderform. 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_get_orderform 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 →