Get inventory information for a SKU
AI agents call vtex_get_inventory 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 performs a query operation to retrieve inventory data without side effects. It does not create, modify, delete, or execute any operations—it only fetches existing information from the VTEX platform. This is a straightforward read operation with minimal security risk.
From the tool's definition Tool name explicitly states 'get_inventory' and description confirms it retrieves 'inventory information for a SKU' with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
Get inventory information for a SKU. 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_inventory: 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_inventory 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_inventory 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_inventory. 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_inventory 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 →