List meal plans. Optional: from_date, to_date (YYYY-MM-DD), page, page_size
AI agents call list_meal_plans to retrieve information from Tandoor 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 and queries meal plan data with optional date range and pagination filters. It has no side effects, does not modify or delete data, and does not execute external operations or trigger financial transactions. It is a straightforward read operation on the Tandoor recipe management system.
From the tool's definition Tool name 'list_meal_plans' and description 'List meal plans' with optional filtering parameters (from_date, to_date, page, page_size) indicates retrieval and querying of existing data without modification or deletion.
Attacks that exploit this kind of access
List meal plans. Optional: from_date, to_date (YYYY-MM-DD), page, page_size. It is categorised as a Read tool in the Tandoor MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Tandoor MCP Server MCP server in PolicyLayer and add a rule for list_meal_plans: 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 Tandoor MCP Server. Nothing to install.
list_meal_plans 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 list_meal_plans 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 list_meal_plans. 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.
list_meal_plans is provided by the Tandoor MCP Server MCP server (mc-mario/tandoor-mcp). 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 →