AI agents use picnic_set_delivery_slot to create or update resources in MCP Picnic — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Picnic environment.
Selecting a delivery slot modifies the user's order state and scheduling preferences, but the action is reversible (can be changed or cancelled later, as evidenced by the sibling tool 'picnic_cancel_delivery'). It does not delete data irreversibly, execute arbitrary code, or commit financial transactions directly.
From the tool's definition Tool name 'picnic_set_delivery_slot' and description 'Select a delivery time slot' indicate modification of delivery scheduling. This is a Write action—it creates or modifies a delivery appointment reversibly.
Documented attack patterns abuse exactly the kind of access picnic_set_delivery_slot gives an agent:
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_set_delivery_slot:
{
"version": "1",
"default": "deny",
"tools": {
"picnic_set_delivery_slot": {
"limits": [
{
"counter": "picnic_set_delivery_slot_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}picnic_set_delivery_slot 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.
Free to start. No card required.
Select a delivery time slot. It is categorised as a Write tool in the MCP Picnic MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Picnic MCP server in PolicyLayer and add a rule for picnic_set_delivery_slot: 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.
picnic_set_delivery_slot 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 picnic_set_delivery_slot 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 picnic_set_delivery_slot. 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.
picnic_set_delivery_slot 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.
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.