get_product_details

Get full details for one product by its handle: variants, SKUs, options, prices, images, and spec metafields. Open tool — no API key required.

SERVERFiltrous MCP Catalog Server SOURCEhttps://filtrous-mcp-catalog.filtrous.workers.dev/mcp

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/com-filtrous-mcp-catalog/get-product-details.md

WHAT IT DOES

What get_product_details does on Filtrous MCP Catalog Server

AI agents call get_product_details to retrieve information from Filtrous MCP Catalog Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`handle`	string	Yes	The product handle (slug), e.g. from search_products.

Parameters from the server's own tool schema.

RISK

Why get_product_details is rated Low

This is a read-only data retrieval operation. It queries and returns product catalog details without side effects, modification capabilities, or irreversible actions. The blast radius of misuse is minimal—an agent could retrieve product information repeatedly but cannot modify inventory, execute commands, or incur financial obligations.

From the tool's definition Tool retrieves product information (variants, SKUs, options, prices, images, spec metafields) by product handle. Action verbs are 'Get' and 'retrieve' with no mention of modification, deletion, or execution.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_product_details safely

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

get_product_details Allowed

get_product_details 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_details": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect Filtrous MCP Catalog Server, apply this rule, and every get_product_details call is checked against it from then on.

FAQ

Questions about get_product_details

What does the get_product_details tool do? +

Get full details for one product by its handle: variants, SKUs, options, prices, images, and spec metafields. Open tool — no API key required. It is categorised as a Read tool in the Filtrous MCP Catalog Server MCP Server, which means it retrieves data without modifying state.

What parameters does get_product_details accept? +

get_product_details accepts 1 parameter: handle. Required: handle. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_product_details? +

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

What risk level is get_product_details? +

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

Can I rate-limit get_product_details? +

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

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

get_product_details is provided by the Filtrous MCP Catalog Server MCP server (https://filtrous-mcp-catalog.filtrous.workers.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Filtrous MCP Catalog Server, and thousands of servers like it.

This server

All 4 Filtrous MCP Catalog Server tools →

Across the catalogue

shopify_get_product on AIVA MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server → The MCP Attack Database →

Guides

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