根据菜谱名称或ID查询指定菜谱的完整详情，包括食材、步骤等
AI agents call mcp_howtocook_getRecipeById 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 is a straightforward retrieval operation that queries a recipe database and returns recipe information (ingredients, cooking steps). No data is created, modified, deleted, or executed. It has no side effects or blast radius if misused by an AI agent—at worst, it retrieves unwanted recipe data. This clearly falls under the Read category.
From the tool's definition Tool retrieves recipe details by name or ID ('根据菜谱名称或ID查询指定菜谱的完整详情，包括食材、步骤等' = 'query complete details of specified recipe by recipe name or ID, including ingredients, steps, etc.').
Attacks that exploit this kind of access
根据菜谱名称或ID查询指定菜谱的完整详情，包括食材、步骤等. 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_getRecipeById: 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_getRecipeById 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_getRecipeById 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_getRecipeById. 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_getRecipeById is provided by the HowToCook-MCP Server MCP server (kureha4/mcptest1). 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 →