Get all product and SKU IDs (useful for indexing)
AI agents call vtex_get_product_and_sku_ids 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 product and SKU identifier data from the VTEX catalog. The 'Get' verb and the stated purpose of 'indexing' (a read-only operation) confirm it is a query/fetch operation with no side effects.
From the tool's definition Tool name 'vtex_get_product_and_sku_ids' and description 'Get all product and SKU IDs (useful for indexing)' indicate a retrieval operation that queries and lists existing data without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
Get all product and SKU IDs (useful for indexing). 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_product_and_sku_ids: 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_product_and_sku_ids 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_product_and_sku_ids 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_product_and_sku_ids. 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_product_and_sku_ids 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 →