AI agents call mcp_howtocook_getAllRecipes to retrieve information from HowToCook-MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves recipe information from the HowToCook repository. It performs a read-only query operation with no data modification, deletion, code execution, or financial implications. The blast radius of misuse is minimal—an AI agent could retrieve all recipes repeatedly but cannot alter, delete, or cause harm with this operation. Classified as Read with low severity.
From the tool's definition Tool name 'getAllRecipes' and description '获取所有菜谱' (get all recipes) indicate a retrieval operation that queries and returns recipe data without modification or side effects.
Documented attack patterns abuse exactly the kind of access mcp_howtocook_getAllRecipes gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and HowToCook-MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for mcp_howtocook_getAllRecipes:
{
"version": "1",
"default": "deny",
"tools": {
"mcp_howtocook_getAllRecipes": {}
}
} mcp_howtocook_getAllRecipes is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
获取所有菜谱. It is categorised as a Read tool in the HowToCook-MCP Server MCP Server, which means it retrieves data without modifying state.
Register the HowToCook-MCP Server MCP server in PolicyLayer and add a rule for mcp_howtocook_getAllRecipes: 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 HowToCook-MCP Server. Nothing to install.
mcp_howtocook_getAllRecipes 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 mcp_howtocook_getAllRecipes 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 mcp_howtocook_getAllRecipes. 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.
mcp_howtocook_getAllRecipes is provided by the HowToCook-MCP Server MCP server (worryzyy/howtocook-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 5 HowToCook-MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
5 HowToCook-MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.