激活(重新打开)Bug,对应禅道 API v1:POST /bugs/{id}/active。适用于已解决/已关闭后重新激活。
AI agents use activateBug to create or update resources in ZenTao MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ZenTao MCP Server environment.
This tool modifies existing bug records by changing their status from resolved/closed to active, which is a write operation. It uses POST, indicating state change rather than retrieval. The action is reversible (bugs can be closed again), so it does not qualify as Destructive.
From the tool's definition Tool description states 'POST /bugs/{id}/active' which is an HTTP POST request that modifies bug status. The Chinese description '激活(重新打开)Bug' translates to 'activate (reopen) bug', indicating state modification.
Attacks that exploit this kind of access
激活(重新打开)Bug,对应禅道 API v1:POST /bugs/{id}/active。适用于已解决/已关闭后重新激活。. It is categorised as a Write tool in the ZenTao MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ZenTao MCP Server MCP server in PolicyLayer and add a rule for activateBug: 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.
activateBug is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the activateBug 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 activateBug. 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.
activateBug is provided by the ZenTao MCP Server MCP server (wudidada/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 →