get_bug_detail

Get bug detail by ID.

Server Zentao @aipper/zentao-mcp-server
Category Read
Risk class Low
Parameters 00 required

What get_bug_detail does on Zentao

AI agents call get_bug_detail 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.

Why get_bug_detail needs a policy

This tool retrieves information about a bug without altering state. It is a straightforward query operation that fetches and returns existing data. The low severity reflects minimal risk from misuse—an AI agent retrieving bug details poses no blast radius beyond potential information disclosure of what is already stored in the ZenTao system.

From the tool's definition Tool name 'get_bug_detail' and description 'Get bug detail by ID' indicate data retrieval with no modification or side effects.

Questions about get_bug_detail

What does the get_bug_detail tool do? +

Get bug detail by ID. It is categorised as a Read tool in the Zentao MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_bug_detail? +

Register the Zentao MCP server in PolicyLayer and add a rule for get_bug_detail: 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.

What risk level is get_bug_detail? +

get_bug_detail is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_bug_detail? +

Yes. Add a rate_limit block to the get_bug_detail 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.

How do I block get_bug_detail completely? +

Set action: deny in the PolicyLayer policy for get_bug_detail. 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.

What MCP server provides get_bug_detail? +

get_bug_detail 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.