resolve_bug · Zentao MCP: Risk & Policy

WHAT IT DOES

What resolve_bug does on Zentao

AI agents use resolve_bug to create or update resources in Zentao — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Zentao environment.

WHY IT NEEDS A POLICY

Why resolve_bug needs a policy

Resolving a bug changes its status reversibly—the bug record remains, its state is updated, and the action can typically be undone by reopening or changing the resolution status. This is a Write operation rather than Destructive.

From the tool's definition Tool name 'resolve_bug' and description 'Resolve one bug by ID' indicate the tool modifies bug state from unresolved to resolved. The phrase 'default resolution=fixed' confirms this is a state change operation.

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

resolve_bug Rate-limited

resolve_bug stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "resolve_bug": {
      "limits": [
        {
          "counter": "resolve_bug_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Zentao, so you can run agents against it safely.

FAQ

Questions about resolve_bug

What does the resolve_bug tool do? +

Resolve one bug by ID (default resolution=fixed). Prefer a solution that explains root cause, fix approach, and logic changes. It is categorised as a Write tool in the Zentao MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on resolve_bug? +

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

resolve_bug is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit resolve_bug? +

Yes. Add a rate_limit block to the resolve_bug 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 resolve_bug completely? +

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

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