Fetch a bug by ID from the given provider.
AI agents call get_bug 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 retrieves bug information by ID from a specified provider. It performs a query operation that returns data without modifying, deleting, or executing anything. This is a straightforward read-only data access pattern. The low severity reflects minimal blast radius—misuse would retrieve unwanted bug data but cause no damage or side effects.
From the tool's definition Tool name is 'get_bug' with description 'Fetch a bug by ID from the given provider.' The verb 'Fetch' indicates data retrieval with no side effects.
Attacks that exploit this kind of access
Fetch a bug by ID from 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 get_bug: 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.
get_bug 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_bug 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 get_bug. 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_bug 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 →