Mark grocery list rows as purchased.
AI agents use mark_grocery_bought 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.
This tool modifies data (grocery list item state) reversibly—marking an item as bought can be undone by unmarking it. It does not permanently delete data, execute code, move money, or create irreversible changes. The blast radius is minimal: worst case, grocery list state becomes temporarily inconsistent until corrected. Hence it is Write, not Destructive or higher.
From the tool's definition Tool name 'mark_grocery_bought' and description 'Mark grocery list rows as purchased' indicate state modification of grocery list items from unpurchased to purchased status.
Attacks that exploit this kind of access
Mark grocery list rows as purchased. 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 mark_grocery_bought: 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.
mark_grocery_bought 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 mark_grocery_bought 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 mark_grocery_bought. 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.
mark_grocery_bought 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 →