Low Risk

browse_vendor

Browse CVEs by vendor name with summary statistics

Part of the Cyreslab Circl Cve Search MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call browse_vendor to retrieve information from Cyreslab Circl Cve Search 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 browse_vendor 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.

cyreslab-circl-cve-search.yaml
tools:
  browse_vendor:
    rules:
      - action: allow

See the full Cyreslab Circl Cve Search policy for all 4 tools.

Tool Name browse_vendor
Category Read
Risk Level Low

Agents calling read-class tools like browse_vendor have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the browse_vendor tool do? +

Browse CVEs by vendor name with summary statistics. It is categorised as a Read tool in the Cyreslab Circl Cve Search MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on browse_vendor? +

Add a rule in your Intercept YAML policy under the tools section for browse_vendor. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Cyreslab Circl Cve Search MCP server.

What risk level is browse_vendor? +

browse_vendor is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit browse_vendor? +

Yes. Add a rate_limit block to the browse_vendor 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.

How do I block browse_vendor completely? +

Set action: deny in the Intercept policy for browse_vendor. 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.

What MCP server provides browse_vendor? +

browse_vendor is provided by the Cyreslab Circl Cve Search MCP server (@iflow-mcp/cyreslab-circl-cve-search-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.