batch_resolve_my_bugs · Zentao MCP: Risk & Policy

WHAT IT DOES

What batch_resolve_my_bugs does on Zentao

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

This tool modifies bug records by changing their status and resolution fields. While it updates data (Write category), it is reversible—bugs can be reopened or status changed again. It affects multiple records in batch, increasing blast radius compared to single-bug operations. However, it does not delete data (not Destructive) or execute arbitrary code (not Execute).

From the tool's definition Tool description explicitly states 'Batch resolve my bugs' with parameters for status and resolution, indicating modification of bug records. The term 'resolve' combined with status and resolution parameters shows this creates or updates bug state reversibly.

Risk signalsBulk/mass operation — affects multiple targets · Admin/system-level operation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

batch_resolve_my_bugs Rate-limited

batch_resolve_my_bugs 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": {
    "batch_resolve_my_bugs": {
      "limits": [
        {
          "counter": "batch_resolve_my_bugs_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 batch_resolve_my_bugs

What does the batch_resolve_my_bugs tool do? +

Batch resolve my bugs (default status=active, resolution=fixed). Prefer projectSetId or /my/bug for project-set scope, and use a shared solution that explains the common root cause 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 batch_resolve_my_bugs? +

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

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

Can I rate-limit batch_resolve_my_bugs? +

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

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

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