markBugResolved · ZenTao MCP Server MCP: Risk & Policy

WHAT IT DOES

What markBugResolved does on ZenTao MCP Server

AI agents use markBugResolved 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.

WHY IT NEEDS A POLICY

Why markBugResolved needs a policy

This tool modifies bug data but does not delete or destroy information—the bug record remains and its status can be reverted. It is therefore Write rather than Destructive. Severity is medium because misuse could incorrectly mark bugs as resolved, disrupting project workflow and hiding unresolved issues, but the operation is reversible and does not affect financial systems or cause data loss.

From the tool's definition Tool name 'markBugResolved' and description 'Mark a bug as resolved' indicate state modification of a bug record. The action changes a bug's status/resolution field to 'fixed', which is a reversible data modification (the status can be changed again).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

markBugResolved Rate-limited

markBugResolved 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": {
    "markBugResolved": {
      "limits": [
        {
          "counter": "markbugresolved_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 MCP Server, so you can run agents against it safely.

FAQ

Questions about markBugResolved

What does the markBugResolved tool do? +

Mark a bug as resolved (resolution=fixed). 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.

How do I enforce a policy on markBugResolved? +

Register the ZenTao MCP Server MCP server in PolicyLayer and add a rule for markBugResolved: 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.

What risk level is markBugResolved? +

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

Can I rate-limit markBugResolved? +

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

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

markBugResolved is provided by the ZenTao MCP Server MCP server (valiant-cat/zentao-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.