Submit a new bug to the given provider.
AI agents use submit_bug to create or update resources in Ubuntu MCP Servers — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ubuntu MCP Servers environment.
This tool creates a new bug report, which is a reversible write operation. It modifies state by adding data to the Ubuntu bug tracking system but does not delete, destroy, or execute arbitrary code. The severity is medium because bugspam or malicious bug submissions could disrupt the bug tracker and waste developer resources, but the action is reversible (submitted bugs can be closed/deleted).
From the tool's definition Tool name 'submit_bug' and description 'Submit a new bug to the given provider' indicate creation of new data (a bug report) in an external system.
Attacks that exploit this kind of access
Submit a new bug to the given provider. It is categorised as a Write tool in the Ubuntu MCP Servers MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ubuntu MCP Servers MCP server in PolicyLayer and add a rule for submit_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.
submit_bug is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the submit_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 submit_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.
submit_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 →