verify_bug · Zentao MCP: Risk & Policy

WHAT IT DOES

What verify_bug does on Zentao

AI agents use verify_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 verify_bug needs a policy

This tool changes the state of a bug (either closing it or reactivating it based on verification result). These are reversible state transitions in a bug tracking workflow — a closed bug can be reopened and vice versa — making Write the most appropriate category rather than Destructive. The blast radius is medium since misuse could disrupt bug workflow but no data is permanently lost.

From the tool's definition Verify bug result: pass -> close, fail -> activate

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

verify_bug Rate-limited

verify_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": {
    "verify_bug": {
      "limits": [
        {
          "counter": "verify_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 verify_bug

What does the verify_bug tool do? +

Verify bug result: pass -> close, fail -> activate. 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 verify_bug? +

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

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

Can I rate-limit verify_bug? +

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

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

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