Get the first active bug assigned to me in a product (by productName). Returns full bug detail.
AI agents call getMyBug 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 from the ZenTao system without creating, modifying, deleting, or executing anything. It is a simple query operation that returns data about bugs assigned to the authenticated user. The only potential data exposure risk is access to bug details, which constitutes a low-severity read operation.
From the tool's definition Tool name 'getMyBug' and description 'Get the first active bug assigned to me in a product...Returns full bug detail' indicate a retrieval operation with no modification or destructive capability.
Attacks that exploit this kind of access
Get the first active bug assigned to me in a product (by productName). Returns full bug detail. 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 getMyBug: 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.
getMyBug 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 getMyBug 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 getMyBug. 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.
getMyBug 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 →