recipe_get
Returns the full manifest of a recipe by name. recipe_not_found if unknown.
This record as markdown: /tools/com-local-mcp-local-mcp/recipe-get.md
What recipe_get does on Local
AI agents call recipe_get to retrieve information from Local without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes |
Parameters from the server's own tool schema.
Why recipe_get is rated Low
This tool retrieves and returns data (a recipe manifest) based on a query parameter (recipe name). It is a read-only operation that does not modify, execute, delete, or commit any financial transactions. The only potential side effect is a not-found error, which is informational. Low severity because recipe data access has minimal blast radius even if an AI agent calls it with arbitrary arguments.
From the tool's definition Tool name 'recipe_get' and description 'Returns the full manifest of a recipe by name' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs recipe_get safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For recipe_get, this is the rule to start with:
recipe_get 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 Local, apply this rule, and every recipe_get call is checked against it from then on.
Questions about recipe_get
Returns the full manifest of a recipe by name. recipe_not_found if unknown. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
recipe_get accepts 1 parameter: name. Required: name. The full parameter table on this page comes from the server's own tool schema.
Register the Local MCP server in PolicyLayer and add a rule for recipe_get: 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 Local. Nothing to install.
recipe_get 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_get 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_get. 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_get is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Local, and thousands of servers like it.
This server
Across the catalogue