AI agents call picnic_get_order_status to retrieve information from MCP Picnic without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns order status information without modifying, creating, deleting, or executing any actions. It is purely informational (Read category). The severity is low because accessing order status data poses minimal risk—it returns existing information without financial, destructive, or operational consequences.
From the tool's definition Tool name 'picnic_get_order_status' and description 'Get the status of a specific order' indicate a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access picnic_get_order_status 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_get_order_status:
{
"version": "1",
"default": "deny",
"tools": {
"picnic_get_order_status": {}
}
}picnic_get_order_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the status of a specific order. It is categorised as a Read tool in the MCP Picnic MCP Server, which means it retrieves data without modifying state.
Register the MCP Picnic MCP server in PolicyLayer and add a rule for picnic_get_order_status: 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_get_order_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the picnic_get_order_status 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_get_order_status. 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_get_order_status 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.