Low Risk

get_product_info

Gets detailed info for a product: nutritional values (macros per 100g), weight/grammage, ingredients, and price.

How to control get_product_info ↓

What get_product_info does on Frisco MCP

AI agents call get_product_info 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.

Low Risk

Why get_product_info needs a policy

This tool retrieves and queries product information from the grocery store database without creating, modifying, deleting, or executing any operations. It has no capability to alter cart state, process payments, or trigger external actions. The data returned is public product metadata. This is a straightforward Read operation with minimal security risk.

From the tool's definition Tool description explicitly states it 'Gets detailed info' for products including nutritional values, weight, ingredients, and price. The verb 'Gets' and the nature of the data (static product information) indicate a retrieval operation with no side effects.

Documented attack patterns abuse exactly the kind of access get_product_info gives an agent:

How to control get_product_info

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 get_product_info:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_product_info": {}
  }
}

get_product_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Frisco MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_product_info

What does the get_product_info tool do? +

Gets detailed info for a product: nutritional values (macros per 100g), weight/grammage, ingredients, and price. It is categorised as a Read tool in the Frisco MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_product_info? +

Register the Frisco MCP server in PolicyLayer and add a rule for get_product_info: 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.

What risk level is get_product_info? +

get_product_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_product_info? +

Yes. Add a rate_limit block to the get_product_info 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.

How do I block get_product_info completely? +

Set action: deny in the PolicyLayer policy for get_product_info. 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.

What MCP server provides get_product_info? +

get_product_info 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.

Enforce policy on every Frisco MCP tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.