AI agents call get_meals_for_range to retrieve information from Yazio MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a query/retrieval tool that accesses food log data with no side effects. It fits the 'Read' category. Severity is low because the data returned is personal nutrition information with limited blast radius if misused. Confidence is 0.85 rather than higher because the tool description is empty, so inference relies on naming convention and sibling tool patterns.
From the tool's definition Tool name 'get_meals_for_range' indicates a retrieval operation. The server description states the purpose is 'querying Yazio food logs including meals, daily summaries, and nutrition totals.' Sibling tools (get_daily_summary, get_diet_schedule,…
Attacks that exploit this kind of access
get_meals_for_range. It is categorised as a Read tool in the Yazio MCP MCP Server, which means it retrieves data without modifying state.
Register the Yazio MCP server in PolicyLayer and add a rule for get_meals_for_range: 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 Yazio MCP. Nothing to install.
get_meals_for_range 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_meals_for_range 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_meals_for_range. 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_meals_for_range is provided by the Yazio MCP server (psilolouben/yazio_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 →