Creates a shopping list for a recipe.
AI agents use create_shopping_list to create or update resources in Recettes MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Recettes MCP Server environment.
This tool creates a new shopping list artifact, which is a reversible write operation. It modifies state by adding a new shopping list record to the system, but causes no deletion, financial transaction, or code execution. The blast radius is minimal—a user could create duplicate or unwanted shopping lists, but these can be easily deleted or ignored.
From the tool's definition Tool name 'create_shopping_list' combined with description 'Creates a shopping list' indicates creation of new data (shopping list document/record).
Attacks that exploit this kind of access
Creates a shopping list for a recipe. It is categorised as a Write tool in the Recettes MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Recettes MCP Server MCP server in PolicyLayer and add a rule for create_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 Recettes MCP Server. Nothing to install.
create_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 create_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 create_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.
create_shopping_list is provided by the Recettes MCP Server MCP server (symfomany/mcp-tuto). 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 →