Critical Risk →

remove_shopping_list_item

Remove an item from your shopping list.

How to control remove_shopping_list_item ↓

AI agents call remove_shopping_list_item to permanently remove resources in MCP Grocy API — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

An AI agent that decides to call remove_shopping_list_item doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from MCP Grocy API is gone — there is no undo for destructive operations.

Documented attack patterns abuse exactly the kind of access remove_shopping_list_item gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Grocy API, and nothing reaches the server without passing your rules. This is the rule we recommend for remove_shopping_list_item:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "remove_shopping_list_item"
  ]
}

remove_shopping_list_item disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register MCP Grocy API — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the remove_shopping_list_item tool do? +

Remove an item from your shopping list. It is categorised as a Destructive tool in the MCP Grocy API MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on remove_shopping_list_item? +

Register the MCP Grocy API MCP server in PolicyLayer and add a rule for remove_shopping_list_item: 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 MCP Grocy API. Nothing to install.

What risk level is remove_shopping_list_item? +

remove_shopping_list_item is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit remove_shopping_list_item? +

Yes. Add a rate_limit block to the remove_shopping_list_item 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.

How do I block remove_shopping_list_item completely? +

Set action: deny in the PolicyLayer policy for remove_shopping_list_item. 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.

What MCP server provides remove_shopping_list_item? +

remove_shopping_list_item is provided by the MCP Grocy API MCP server (saya6k/mcp-grocy-api). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Grocy API tool call.

Deterministic rules across all 37 MCP Grocy API tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

37 MCP Grocy API tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.