mcp_kulinar_getRecipeById
Возвращает полный рецепт по id или названию блюда (с ингредиентами, шагами, временем).
This record as markdown: /tools/cowork-bench/mcp-kulinar-getrecipebyid.md
What mcp_kulinar_getRecipeById does on Cowork Bench
AI agents call mcp_kulinar_getRecipeById to retrieve information from Cowork Bench without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why mcp_kulinar_getRecipeById is rated Low
This tool retrieves recipe information (ingredients, steps, time) based on an identifier or name. It is a query/fetch operation that returns data without creating, modifying, or deleting any resources. No external operations, financial transactions, or code execution are involved. This is a straightforward Read operation with minimal risk if misused by an agent.
From the tool's definition Tool name 'getRecipeById' and description 'Возвращает полный рецепт по id или названию блюда' (Returns full recipe by id or dish name) indicate retrieval of existing data with no modification, deletion, or side effects.
Attacks that exploit this kind of access
The rule that runs mcp_kulinar_getRecipeById safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Cowork Bench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mcp_kulinar_getRecipeById, this is the rule to start with:
mcp_kulinar_getRecipeById is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Cowork Bench, apply this rule, and every mcp_kulinar_getRecipeById call is checked against it from then on.
Questions about mcp_kulinar_getRecipeById
Возвращает полный рецепт по id или названию блюда (с ингредиентами, шагами, временем). It is categorised as a Read tool in the Cowork Bench MCP Server, which means it retrieves data without modifying state.
Register the Cowork Bench MCP server in PolicyLayer and add a rule for mcp_kulinar_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 Cowork Bench. Nothing to install.
mcp_kulinar_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_kulinar_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_kulinar_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_kulinar_getRecipeById is provided by the Cowork Bench MCP server (0717376/cowork_bench). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Cowork Bench, and thousands of servers like it.
This server
Across the catalogue