get_known_bugs

Non-CVE known bugs for a specific package version. USE WHEN: unexpected behavior that is NOT a security issue; a pinned version misbehaves. RETURNS: {bugs[]: {title, fixed_in, workaround}}.

SERVERDepscope SOURCEcuttalo/depscope-mcp

Low RISK CLASS

Category Read

Parameters 32 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/dev-depscope-mcp/get-known-bugs.md

WHAT IT DOES

What get_known_bugs does on Depscope

AI agents call get_known_bugs to retrieve information from Depscope 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
`package`	string	Yes
`version`	string	—
`ecosystem`	string	Yes

Parameters from the server's own tool schema.

RISK

Why get_known_bugs is rated Low

This tool retrieves and queries known bug information for package versions without creating, modifying, deleting, or executing any operations. It is purely informational, similar to documentation lookup. The modest severity reflects that misuse would at worst provide incomplete troubleshooting guidance rather than enable harmful actions.

From the tool's definition Tool name 'get_known_bugs' and description 'Non-CVE known bugs for a specific package version' with return value {bugs[]: {title, fixed_in, workaround}} indicate retrieval of information only.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_known_bugs safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Depscope, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_known_bugs, this is the rule to start with:

get_known_bugs Allowed

get_known_bugs is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_known_bugs": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Depscope, apply this rule, and every get_known_bugs call is checked against it from then on.

FAQ

Questions about get_known_bugs

What does the get_known_bugs tool do? +

Non-CVE known bugs for a specific package version. USE WHEN: unexpected behavior that is NOT a security issue; a pinned version misbehaves. RETURNS: {bugs[]: {title, fixed_in, workaround}}. It is categorised as a Read tool in the Depscope MCP Server, which means it retrieves data without modifying state.

What parameters does get_known_bugs accept? +

get_known_bugs accepts 3 parameters: package, version, ecosystem. Required: package, ecosystem. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_known_bugs? +

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

What risk level is get_known_bugs? +

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

Can I rate-limit get_known_bugs? +

Yes. Add a rate_limit block to the get_known_bugs 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 get_known_bugs completely? +

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

get_known_bugs is provided by the Depscope MCP server (cuttalo/depscope-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Depscope, and thousands of servers like it.

This server

All 22 Depscope tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →