get_product

Get full product details by ID: name, description, price, variations, images, attributes, SEO, etc.

SERVERWebcake Storefront SOURCEwebcake-storefront-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/webcake-storefront/get-product.md

WHAT IT DOES

What get_product does on Webcake Storefront

AI agents call get_product to retrieve information from Webcake Storefront without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_product is rated Low

This tool queries and returns product information without creating, modifying, deleting, or executing operations. It is a straightforward data retrieval operation with no side effects, fitting the Read category. Low severity because unauthorized access to product details poses minimal direct harm compared to tools that can modify inventory, process payments, or delete data.

From the tool's definition Tool name is 'get_product' and description states it 'Get full product details by ID' with no modification or deletion language. It retrieves data only.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_product safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Webcake Storefront, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_product, this is the rule to start with:

get_product Allowed

get_product is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_product": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Webcake Storefront, apply this rule, and every get_product call is checked against it from then on.

FAQ

Questions about get_product

What does the get_product tool do? +

Get full product details by ID: name, description, price, variations, images, attributes, SEO, etc. It is categorised as a Read tool in the Webcake Storefront MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_product? +

Register the Webcake Storefront 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 Webcake Storefront. 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 Webcake Storefront MCP server (webcake-storefront-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Webcake Storefront, and thousands of servers like it.

This server

All 287 Webcake Storefront tools →

Across the catalogue

shopify_get_product on AIVA MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →