Send or resend the invoice email for a completed delivery
AI agents use picnic_send_delivery_invoice_email 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 creates or triggers a write action (sending an email) with reversible effects—the email can be unsent or marked as spam, and it does not delete data or execute arbitrary code. However, it has medium severity because unsolicited emails could constitute spam/harassment if misused by an AI agent, and it interacts with external systems.
From the tool's definition Tool name 'picnic_send_delivery_invoice_email' and description 'Send or resend the invoice email for a completed delivery' indicate the tool sends/triggers email communication, which modifies email logs and triggers external email system actions.
Documented attack patterns abuse exactly the kind of access picnic_send_delivery_invoice_email 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_send_delivery_invoice_email:
{
"version": "1",
"default": "deny",
"tools": {
"picnic_send_delivery_invoice_email": {
"limits": [
{
"counter": "picnic_send_delivery_invoice_email_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}picnic_send_delivery_invoice_email 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.
Send or resend the invoice email for 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_send_delivery_invoice_email: 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_send_delivery_invoice_email 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_send_delivery_invoice_email 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_send_delivery_invoice_email. 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_send_delivery_invoice_email 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.