Low Risk

get_product

Get a single product by ID, including its variants, options, and images.

How to control get_product ↓

What get_product does on Sapo

AI agents call get_product to retrieve information from Sapo 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 needs a policy

This tool retrieves product information (ID, variants, options, images) from the e-commerce platform without creating, modifying, deleting, or executing any operations. It is a straightforward read-only query operation with minimal blast radius if misused by an AI agent.

From the tool's definition Tool name 'get_product' and description 'Get a single product by ID, including its variants, options, and images' indicates data retrieval with no modification or side effects.

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

How to control get_product

PolicyLayer is an MCP gateway — it sits between your AI agents and Sapo, and nothing reaches the server without passing your rules. This is the rule we recommend for get_product:

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

get_product 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 Sapo — 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

What does the get_product tool do? +

Get a single product by ID, including its variants, options, and images. It is categorised as a Read tool in the Sapo MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_product? +

Register the Sapo MCP server in PolicyLayer and add a rule for get_product: 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 Sapo. Nothing to install.

What risk level is get_product? +

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

Can I rate-limit get_product? +

Yes. Add a rate_limit block to the get_product 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 completely? +

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

get_product is provided by the Sapo MCP server (nguyennguyenit/sapo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Sapo tool call.

Start from Sapo, 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.

93 Sapo 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.