Low Risk

search_bugs_by_product_and_release

Search bugs by specific product ID and software releases. CRITICAL: Use

How to control search_bugs_by_product_and_release ↓

AI agents call search_bugs_by_product_and_release to retrieve information from Mcp Cisco Support without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Even though search_bugs_by_product_and_release only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Documented attack patterns abuse exactly the kind of access search_bugs_by_product_and_release gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Cisco Support, and nothing reaches the server without passing your rules. This is the rule we recommend for search_bugs_by_product_and_release:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_bugs_by_product_and_release": {}
  }
}

search_bugs_by_product_and_release is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Mcp Cisco Support — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the search_bugs_by_product_and_release tool do? +

Search bugs by specific product ID and software releases. CRITICAL: Use. It is categorised as a Read tool in the Mcp Cisco Support MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_bugs_by_product_and_release? +

Register the Mcp Cisco Support MCP server in PolicyLayer and add a rule for search_bugs_by_product_and_release: 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 Mcp Cisco Support. Nothing to install.

What risk level is search_bugs_by_product_and_release? +

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

Can I rate-limit search_bugs_by_product_and_release? +

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

How do I block search_bugs_by_product_and_release completely? +

Set action: deny in the PolicyLayer policy for search_bugs_by_product_and_release. 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 search_bugs_by_product_and_release? +

search_bugs_by_product_and_release is provided by the Mcp Cisco Support MCP server (sieteunoseis/mcp-cisco-support). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Cisco Support tool call.

Deterministic rules across all 58 Mcp Cisco Support tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

58 Mcp Cisco Support tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.