comment_bug · Zentao MCP: Risk & Policy

WHAT IT DOES

What comment_bug does on Zentao

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

This tool creates new comment records attached to a bug ticket, modifying the bug's state reversibly. While comments can be added to document solutions and analysis, they are not destructive (not deleted/purged irreversibly) and do not execute code or move money.

From the tool's definition Tool name is 'comment_bug' and description states 'Add comment to one bug by ID', which is a create/modify action on existing data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

comment_bug Rate-limited

comment_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": {
    "comment_bug": {
      "limits": [
        {
          "counter": "comment_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 comment_bug

What does the comment_bug tool do? +

Add comment to one bug by ID. For solution updates, explain analysis and logic changes rather than build/test evidence. 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 comment_bug? +

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

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

Can I rate-limit comment_bug? +

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

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

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