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.
This record as markdown: /tools/com-filtrous-mcp-catalog/get-price-and-lead-time.md
What get_price_and_lead_time does on Filtrous MCP Catalog Server
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
sku | string | Yes | The exact product SKU. |
Parameters from the server's own tool schema.
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 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.
Attacks that exploit this kind of access
The rule that runs get_price_and_lead_time 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_price_and_lead_time, this is the rule to start with:
get_price_and_lead_time is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Filtrous MCP Catalog Server, apply this rule, and every get_price_and_lead_time call is checked against it from then on.
Questions about 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. It is categorised as a Read tool in the Filtrous MCP Catalog Server MCP Server, which means it retrieves data without modifying state.
get_price_and_lead_time accepts 1 parameter: sku. Required: sku. The full parameter table on this page comes from the server's own tool schema.
Register the Filtrous MCP Catalog Server MCP server in PolicyLayer and add a rule for get_price_and_lead_time: 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.
get_price_and_lead_time is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_price_and_lead_time 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.
Set action: deny in the PolicyLayer policy for get_price_and_lead_time. 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.
get_price_and_lead_time 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.
More on Filtrous MCP Catalog Server, and thousands of servers like it.
This server
Across the catalogue