Get meal entries and calendar events for a date range (YYYY-MM-DD).
AI agents call get_meal_calendar to retrieve information from CoupleHub 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 or queries existing meal calendar data within a specified date range. It performs no modifications, deletions, executions, or financial operations. The verb 'Get' and the lack of any mutating language confirm this is a read-only operation with minimal risk if misused by an AI agent.
From the tool's definition Tool name 'get_meal_calendar' and description 'Get meal entries and calendar events for a date range' clearly indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Get meal entries and calendar events for a date range (YYYY-MM-DD). It is categorised as a Read tool in the CoupleHub MCP Server MCP Server, which means it retrieves data without modifying state.
Register the CoupleHub MCP Server MCP server in PolicyLayer and add a rule for get_meal_calendar: 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 CoupleHub MCP Server. Nothing to install.
get_meal_calendar 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_meal_calendar 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_meal_calendar. 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_meal_calendar is provided by the CoupleHub MCP Server MCP server (uczesieweba/couplehub-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 →