upsert_meal_calendar
AI agents use upsert_meal_calendar to create or update resources in CoupleHub MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CoupleHub MCP Server environment.
Upsert operations are reversible modifications that create or update records. The blast radius is medium because unintended meal calendar changes could disrupt shared household planning, but can be corrected. This is less severe than Destructive (which cannot be undone) and more severe than Read-only operations.
From the tool's definition Tool name 'upsert_meal_calendar' indicates create-or-update operation on calendar data (upsert = update or insert). Sibling tools include 'create_calendar_event', 'create_recipe', and 'create_item', establishing the Write category pattern.
Attacks that exploit this kind of access
upsert_meal_calendar. It is categorised as a Write tool in the CoupleHub MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the CoupleHub MCP Server MCP server in PolicyLayer and add a rule for upsert_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.
upsert_meal_calendar is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the upsert_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 upsert_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.
upsert_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 →