AI agents use picnic_rate_delivery 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.
This tool submits a rating for a completed delivery, which is a write operation (creates/modifies review data). It has minimal blast radius as it only affects a rating score on a past delivery, with no financial, destructive, or execution implications.
From the tool's definition Rate a completed delivery
Documented attack patterns abuse exactly the kind of access picnic_rate_delivery 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_rate_delivery:
{
"version": "1",
"default": "deny",
"tools": {
"picnic_rate_delivery": {
"limits": [
{
"counter": "picnic_rate_delivery_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}picnic_rate_delivery 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.
Rate a completed delivery. 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_rate_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.
picnic_rate_delivery 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_rate_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.
Set action: deny in the PolicyLayer policy for picnic_rate_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.
picnic_rate_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.
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.