Search your Old Family Recipe cookbook by keyword, ingredient, or tag.
AI agents call recipe_search to retrieve information from Old Family Recipe without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only search operation on stored recipe data. It retrieves matching records based on search criteria but does not create, modify, delete, or execute any actions. The search capability poses minimal security risk; misuse would only return unwanted recipe information rather than causing harm, data loss, or financial impact.
From the tool's definition Tool name 'recipe_search' and description 'Search your Old Family Recipe cookbook by keyword, ingredient, or tag' indicate a query/retrieval operation with no data modification, deletion, or external side effects.
Attacks that exploit this kind of access
Search your Old Family Recipe cookbook by keyword, ingredient, or tag. It is categorised as a Read tool in the Old Family Recipe MCP Server, which means it retrieves data without modifying state.
Register the Old Family Recipe MCP server in PolicyLayer and add a rule for recipe_search: 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 Old Family Recipe. Nothing to install.
recipe_search 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 recipe_search 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 recipe_search. 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.
recipe_search is provided by the Old Family Recipe MCP server (oldfamilyrecipe/ai). 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 →