Get the next active bug assigned to me under a product (first match).
AI agents call getNextBug to retrieve information from ZenTao 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 bug information without side effects. It queries the ZenTao system to fetch the next unresolved bug matching specified criteria, similar to other Read operations like getBugDetail, getMyBug, and getMyBugs on the same server. The blast radius of misuse is minimal - at worst, an agent could retrieve bugs belonging to the user, but cannot modify, delete, or execute code.
From the tool's definition Tool name and description indicate retrieval only: 'Get the next active bug assigned to me under a product (first match)' - a query operation with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
Get the next active bug assigned to me under a product (first match). It is categorised as a Read tool in the ZenTao MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ZenTao MCP Server MCP server in PolicyLayer and add a rule for getNextBug: 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 ZenTao MCP Server. Nothing to install.
getNextBug 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 getNextBug 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 getNextBug. 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.
getNextBug is provided by the ZenTao MCP Server MCP server (valiant-cat/zentao-mcp-server). 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 →