Get bug detail by ID; also extracts image URLs from steps HTML into stepsImages.
AI agents call getBugDetail 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 modifying, deleting, or executing any operations. It is purely informational, returning details about an existing bug record. The extraction of image URLs is a data transformation on retrieved information, not a state-changing operation. No financial, destructive, or executable actions are performed.
From the tool's definition Tool name 'getBugDetail' and description 'Get bug detail by ID' indicate a retrieval operation with no side effects. The mention of extracting image URLs from steps HTML confirms data retrieval only.
Attacks that exploit this kind of access
Get bug detail by ID; also extracts image URLs from steps HTML into stepsImages. 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 getBugDetail: 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.
getBugDetail 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 getBugDetail 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 getBugDetail. 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.
getBugDetail 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 →