Reject recommended items — already have them.
AI agents use reject_recommended_grocery 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 state (marking items as rejected/having them) without permanently destroying data or triggering external operations. It is reversible—a rejected recommendation could theoretically be re-recommended. The blast radius is minimal: worst case, users temporarily lose visibility of a grocery recommendation, which is easily corrected.
From the tool's definition Tool name 'reject_recommended_grocery' and description 'Reject recommended items — already have them' indicate modification of recommendation state or grocery list status.
Attacks that exploit this kind of access
Reject recommended items — already have them. 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 reject_recommended_grocery: 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.
reject_recommended_grocery 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 reject_recommended_grocery 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 reject_recommended_grocery. 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.
reject_recommended_grocery 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 →