Search for bugs matching criteria on the given provider.
AI agents call search_bugs to retrieve information from Ubuntu MCP Servers without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool searches and retrieves bug data from Ubuntu providers without creating, modifying, deleting, or executing operations. It is a read-only query function that retrieves information based on search criteria. The blast radius if misused by an AI agent is minimal—it can at worst retrieve bug information already public in the system. No side effects, no data modification, no execution, no financial impact.
From the tool's definition Tool name 'search_bugs' and description 'Search for bugs matching criteria on the given provider' indicate a query/retrieval operation with no modification of data.
Attacks that exploit this kind of access
Search for bugs matching criteria on the given provider. It is categorised as a Read tool in the Ubuntu MCP Servers MCP Server, which means it retrieves data without modifying state.
Register the Ubuntu MCP Servers MCP server in PolicyLayer and add a rule for search_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 Ubuntu MCP Servers. Nothing to install.
search_bugs 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 search_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.
Set action: deny in the PolicyLayer policy for search_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.
search_bugs is provided by the Ubuntu MCP Servers MCP server (lvoytek/ubuntu-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →