remove_from_cart · Rohlik MCP: Risk & Policy

WHAT IT DOES

What remove_from_cart does on Rohlik

AI agents use remove_from_cart to create or update resources in Rohlik — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Rohlik environment.

PARAMETERS

Parameter	Type	Required	Description
`order_field_id`	string	Yes	The order field ID of the item to remove (cart_item_id from cart content)

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why remove_from_cart needs a policy

Removing an item from a shopping cart is a reversible write operation; the user can add the item back. It does not delete persistent data, execute code, or involve financial transactions. Severity is medium because an AI agent could inadvertently clear desired items from a user's cart.

From the tool's definition 'Remove an item from the shopping cart' — removes an item but cart modifications are reversible (item can be re-added)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

remove_from_cart Rate-limited

remove_from_cart stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "remove_from_cart": {
      "limits": [
        {
          "counter": "remove_from_cart_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Rohlik, so you can run agents against it safely.

FAQ

Questions about remove_from_cart

What does the remove_from_cart tool do? +

Remove an item from the shopping cart. It is categorised as a Write tool in the Rohlik MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does remove_from_cart accept? +

remove_from_cart accepts 1 parameter: order_field_id. Required: order_field_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on remove_from_cart? +

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

What risk level is remove_from_cart? +

remove_from_cart is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit remove_from_cart? +

Yes. Add a rate_limit block to the remove_from_cart 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_from_cart completely? +

Set action: deny in the PolicyLayer policy for remove_from_cart. 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_from_cart? +

remove_from_cart is provided by the Rohlik MCP server (@tomaspavlin/rohlik-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.