This record as markdown: /tools/graysoncadams-mealie-mcp/get-tool.md
What get_tool does on Mealie MCP Server
AI agents call get_tool to retrieve information from Mealie MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_tool is rated Low
This tool retrieves a specific recipe tool/item from the Mealie instance by its identifier. It is a simple lookup operation that queries existing data without creating, modifying, deleting, or executing anything. The blast radius is minimal—it only exposes recipe data already accessible to the authenticated user.
From the tool's definition Tool name 'get_tool' with description 'Get a specific recipe tool by ID' indicates data retrieval. The verb 'Get' and context of querying by ID are characteristic of read-only operations with no side effects.
Attacks that exploit this kind of access
The rule that runs get_tool safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mealie MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_tool, this is the rule to start with:
get_tool 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 Mealie MCP Server, apply this rule, and every get_tool call is checked against it from then on.
Questions about get_tool
Get a specific recipe tool by ID. It is categorised as a Read tool in the Mealie MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Mealie MCP Server MCP server in PolicyLayer and add a rule for get_tool: 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 Mealie MCP Server. Nothing to install.
get_tool 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 get_tool 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 get_tool. 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.
get_tool is provided by the Mealie MCP Server MCP server (graysoncadams/mealie-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mealie MCP Server, and thousands of servers like it.
This server
Across the catalogue