Search for products in Picnic with pagination and filtered results
AI agents call picnic_search 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 is a straightforward search/query operation that retrieves information about products available in the Picnic supermarket. It does not modify, delete, execute code, or involve financial transactions. The pagination and filtering features are typical of read-only search interfaces.
From the tool's definition Tool description states it "Search[es] for products in Picnic with pagination and filtered results" — a pure data retrieval operation with no side effects. The tool name "picnic_search" and description indicate querying and filtering existing product data.
Documented attack patterns abuse exactly the kind of access picnic_search 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_search:
{
"version": "1",
"default": "deny",
"tools": {
"picnic_search": {}
}
}picnic_search 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.
Search for products in Picnic with pagination and filtered results. 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_search: 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_search 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_search 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_search. 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_search 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.