AI agents call list_recipes to retrieve information from Paprika without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves recipe data with pagination and filtering options. It has no side effects; it does not create, modify, delete, or execute any operations. The operations described (list, paginate, sort, filter, select fields) are all read-only query operations typical of the Read category. Severity is low because unauthorized access to recipe data poses minimal risk to users or systems.
From the tool's definition Tool name is 'list_recipes' and description states it 'List recipes from Paprika with pagination, sorting, filtering, and field selection' — purely retrieves and queries data with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
List recipes from Paprika with pagination, sorting, filtering, and field selection for large collections. It is categorised as a Read tool in the Paprika MCP Server, which means it retrieves data without modifying state.
Register the Paprika MCP server in PolicyLayer and add a rule for list_recipes: 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 Paprika. Nothing to install.
list_recipes 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 list_recipes 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 list_recipes. 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.
list_recipes is provided by the Paprika MCP server (sandordaroczi/paprika-mcp-python-server). 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 →