Critical Risk →

picnic_cancel_delivery

Cancel a delivery order

How to control picnic_cancel_delivery ↓

What picnic_cancel_delivery does on MCP Picnic

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

Critical Risk

Why picnic_cancel_delivery needs a policy

Canceling a delivery order is a destructive action that irreversibly terminates a committed transaction. While not financial in the strict sense (no money changes hands directly), it cancels a financial obligation and cannot be reversed by the tool itself. The most severe category that applies is Destructive, as the action permanently modifies order state in a way that requires external action to restore.

From the tool's definition Tool name 'picnic_cancel_delivery' with description 'Cancel a delivery order' indicates irreversible cancellation of an existing order, which destroys the order state and cannot be undone without manual intervention.

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

How to control picnic_cancel_delivery

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

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

picnic_cancel_delivery 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 Picnic — 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.

Related tools and policies

Go deeper

Questions about picnic_cancel_delivery

What does the picnic_cancel_delivery tool do? +

Cancel a delivery order. It is categorised as a Destructive tool in the MCP Picnic 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 picnic_cancel_delivery? +

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

What risk level is picnic_cancel_delivery? +

picnic_cancel_delivery 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 picnic_cancel_delivery? +

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

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

picnic_cancel_delivery is provided by the MCP Picnic MCP server (ivo-toby/mcp-picnic). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Picnic tool call.

Start from MCP Picnic, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

25 MCP Picnic tools catalogued and risk-classified — across an index of 43,000+ 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.