Full catalog for a specific vendor: all models, modalities, and pricing. Returns vendor metadata (country, region, pricing page URL) plus every model and SKU they offer. Examples: - "What does Together AI sell?" → vendor="Together AI" - "OpenAI's text model pricing" → vendor="OpenAI", modal...
Part of the ATOM Pricing Intelligence MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call get_vendor_catalog to retrieve information from ATOM Pricing Intelligence without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get_vendor_catalog only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
get_vendor_catalog:
rules:
- action: allowSee the full ATOM Pricing Intelligence policy for all 8 tools.
Agents calling read-class tools like get_vendor_catalog have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Full catalog for a specific vendor: all models, modalities, and pricing. Returns vendor metadata (country, region, pricing page URL) plus every model and SKU they offer. Examples: - "What does Together AI sell?" → vendor="Together AI" - "OpenAI's text model pricing" → vendor="OpenAI", modality="Text" - "Amazon Bedrock catalog" → vendor="Amazon Bedrock". It is categorised as a Read tool in the ATOM Pricing Intelligence MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for get_vendor_catalog. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the ATOM Pricing Intelligence MCP server.
get_vendor_catalog 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_vendor_catalog rule in your Intercept 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 Intercept policy for get_vendor_catalog. 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_vendor_catalog is provided by the ATOM Pricing Intelligence MCP server (atom-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept