Searches frisco.pl for products, returns top matches with prices, and saves the search URL/context for add_items_to_cart.
AI agents call search_products to retrieve information from Frisco MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries product information from the e-commerce platform. It has no capability to modify cart state, execute transactions, or alter any stored data. The context-saving is metadata management for subsequent operations, not a modification of the system itself. Searching is a canonical Read operation with minimal security risk.
From the tool's definition Tool description states it 'Searches frisco.pl for products, returns top matches with prices' — purely a search operation with no side effects. The function saves search context for later use but does not modify, create, or delete any data.
Documented attack patterns abuse exactly the kind of access search_products gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Frisco MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for search_products:
{
"version": "1",
"default": "deny",
"tools": {
"search_products": {}
}
} search_products 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.
Searches frisco.pl for products, returns top matches with prices, and saves the search URL/context for add_items_to_cart. It is categorised as a Read tool in the Frisco MCP MCP Server, which means it retrieves data without modifying state.
Register the Frisco MCP server in PolicyLayer and add a rule for search_products: 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 Frisco MCP. Nothing to install.
search_products 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 search_products 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 search_products. 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.
search_products is provided by the Frisco MCP server (mkidawa/frisco-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Frisco MCP, 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.
15 Frisco MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.