AI agents call get_my_bugs to retrieve information from Zentao without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and filters bug data assigned to the user without creating, modifying, deleting, or executing operations. It is a straightforward read-only query with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'get_my_bugs' and description 'List bugs assigned to me' indicates data retrieval with no modification or side effects. The mention of 'supports status/keyword/limit/page filter' confirms it is a query/list operation.
Attacks that exploit this kind of access
List bugs assigned to me (supports status/keyword/limit/page filter). For project-set scope, prefer projectSetId or /my/bug instead of relying on list_my_projects. It is categorised as a Read tool in the Zentao MCP Server, which means it retrieves data without modifying state.
Register the Zentao MCP server in PolicyLayer and add a rule for get_my_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 Zentao. Nothing to install.
get_my_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 get_my_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 get_my_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.
get_my_bugs is provided by the Zentao MCP server (@aipper/zentao-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_my_bugs is one line of Zentao's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →