# get_price_and_lead_time

Get current price, availability, and (when permitted) stock for a SKU. KEYED tool — requires a valid API key. Tier pricing and lead time are placeholders until the Acumatica sync ships.

Agent View of the PolicyLayer registry record for `get_price_and_lead_time`. HTML page: https://policylayer.com/tools/com-filtrous-mcp-catalog/get-price-and-lead-time

## Facts

- Tool: `get_price_and_lead_time`
- 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 |
| --- | --- | --- | --- |
| `sku` | string | yes | The exact product SKU. |

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_price_and_lead_time",
    "arguments": {
      "sku": "<sku>"
    }
  }
}
```

## Why get_price_and_lead_time is rated Low

This tool queries product pricing and inventory information without creating, modifying, deleting, or executing any operations. It requires an API key (access control), but the core function is data retrieval with no side effects. The mention of 'Tier pricing and lead time are placeholders' confirms it returns static/reference data.

From the tool's own definition: "Tool retrieves 'current price, availability, and stock for a SKU' with no modification or execution capability. The description explicitly states it 'Get[s]' data and references 'placeholders', indicating query-only behavior."

## Use case

AI agents call get_price_and_lead_time 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_price_and_lead_time": {}
  }
}
```

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

- `get_product_details` — Read — https://policylayer.com/tools/com-filtrous-mcp-catalog/get-product-details.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