List bugs with optional filtering
AI agents call list_bugs to retrieve information from Follow Plan MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries bug data from the project management system with optional filters applied, producing no side effects. It does not create, modify, delete, execute code, or move money. The blast radius of misuse is minimal—an attacker could only view bug information that may or may not be sensitive depending on deployment context, but cannot alter system state.
From the tool's definition Tool name 'list_bugs' and description 'List bugs with optional filtering' indicate data retrieval with no modification. The 'list' verb and 'filtering' operation are characteristic of read-only query operations.
Attacks that exploit this kind of access
List bugs with optional filtering. It is categorised as a Read tool in the Follow Plan MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Follow Plan MCP Server MCP server in PolicyLayer and add a rule for list_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 Follow Plan MCP Server. Nothing to install.
list_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 list_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 list_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.
list_bugs is provided by the Follow Plan MCP Server MCP server (vibeclasses/follow-plan-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 →