AI agents call voog_ecommerce_api_read to retrieve information from Voog without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool is explicitly constrained to GET requests for read-only API access. It retrieves ecommerce data (products, settings, carts, orders, etc.) without modifying or deleting anything. The read-only nature and GET-only restriction make this a safe retrieval operation with minimal blast radius — an AI agent misusing it could expose sensitive business data but cannot corrupt systems or cause financial harm.
From the tool's definition Tool name explicitly includes 'read-only' and description states 'Read-only Ecommerce v1 API passthrough. Forward a GET' — GET requests retrieve data without side effects.
Attacks that exploit this kind of access
Read-only Ecommerce v1 API passthrough. Forward a GET. It is categorised as a Read tool in the Voog MCP Server, which means it retrieves data without modifying state.
Register the Voog MCP server in PolicyLayer and add a rule for voog_ecommerce_api_read: 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 Voog. Nothing to install.
voog_ecommerce_api_read 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 voog_ecommerce_api_read 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 voog_ecommerce_api_read. 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.
voog_ecommerce_api_read is provided by the Voog MCP server (runnel/voog-mcp). 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 →