tandoor_shopping_list
AI agents use tandoor_shopping_list to create or update resources in Tandoor MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tandoor MCP Server environment.
The server description explicitly states the server allows users to 'update shopping list items', which maps to Write (create or modify data reversibly). The tool name 'tandoor_shopping_list' aligns with managing shopping list entries. However, the tool description is empty, so confidence is reduced.
From the tool's definition Tool name 'tandoor_shopping_list' and server description mentions 'update shopping list items'
Attacks that exploit this kind of access
tandoor_shopping_list. It is categorised as a Write tool in the Tandoor MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Tandoor MCP Server MCP server in PolicyLayer and add a rule for tandoor_shopping_list: 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 Tandoor MCP Server. Nothing to install.
tandoor_shopping_list is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the tandoor_shopping_list 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 tandoor_shopping_list. 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.
tandoor_shopping_list is provided by the Tandoor MCP Server MCP server (oculairmedia/tandoor.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 →