提交 Bug 解决动作(fixed/notrepro/duplicate/...)。
AI agents use resolveBug 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.
The tool creates or modifies bug records by submitting resolution status changes. While it changes state, these modifications are reversible (a bug status can be changed again), making it a Write rather than Destructive action. Medium severity reflects the moderate blast radius: misuse could incorrectly mark bugs as resolved, misleading development workflows, but the action is auditable and reversible.
From the tool's definition Tool submits bug resolution actions (提交 Bug 解决动作) with status transitions like 'fixed', 'notrepro', 'duplicate', etc. This modifies bug state/data in ZenTao.
Attacks that exploit this kind of access
提交 Bug 解决动作(fixed/notrepro/duplicate/...)。. 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 resolveBug: 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.
resolveBug 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 resolveBug 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 resolveBug. 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.
resolveBug 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 →