# request_quote

Submit a quote request for one or more SKUs with buyer contact info. KEYED tool — requires a valid API key. Sales follows up out-of-band.

Agent View of the PolicyLayer registry record for `request_quote`. HTML page: https://policylayer.com/tools/com-filtrous-mcp-catalog/request-quote

## Facts

- Tool: `request_quote`
- 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: Write (Medium risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 3 (2 required)
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `items` | array | yes | Line items to quote. |
| `notes` | string | no | Free-text context / use case. |
| `contact` | object | yes |  |

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": "request_quote",
    "arguments": {
      "items": [],
      "contact": {}
    }
  }
}
```

## Why request_quote is rated Medium

This tool submits a quote request (creates a record/transaction) with buyer contact information. It does not directly move money or commit a financial obligation — it only initiates a sales follow-up process out-of-band. This makes it a Write operation (creating a quote request) rather than Financial. However, misuse could expose buyer contact info or generate unwanted sales outreach, warranting medium severity.

From the tool's own definition: "Submit a quote request for one or more SKUs with buyer contact info. Sales follows up out-of-band."

## Use case

AI agents use request_quote to create or update resources in Filtrous MCP Catalog Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Filtrous MCP Catalog Server environment.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. 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": {
    "request_quote": {
      "limits": [
        {
          "counter": "request_quote_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

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

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