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

Agent View of the PolicyLayer registry record for `get_product_details`. HTML page: https://policylayer.com/tools/com-filtrous-mcp-catalog/get-product-details

## Facts

- Tool: `get_product_details`
- Server: Filtrous MCP Catalog Server (`https://filtrous-mcp-catalog.filtrous.workers.dev/mcp`) — https://policylayer.com/tools/com-filtrous-mcp-catalog.md
- Homepage: https://github.com/https://filtrous-mcp-catalog.filtrous.workers.dev/mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 1 (1 required)
- Recommended policy verdict: Allowed

## Parameters

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

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_product_details",
    "arguments": {
      "handle": "<handle>"
    }
  }
}
```

## 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 own 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."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Filtrous MCP Catalog Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_product_details": {}
  }
}
```

## Other tools on Filtrous MCP Catalog Server (3)

- `get_price_and_lead_time` — Read — https://policylayer.com/tools/com-filtrous-mcp-catalog/get-price-and-lead-time.md
- `search_products` — Read — https://policylayer.com/tools/com-filtrous-mcp-catalog/search-products.md
- `request_quote` — Write — https://policylayer.com/tools/com-filtrous-mcp-catalog/request-quote.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-filtrous-mcp-catalog · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-filtrous-mcp-catalog