update_bug · TAPD MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_bug does on TAPD MCP Server

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

WHY IT NEEDS A POLICY

Why update_bug needs a policy

The tool modifies existing bug data in a tracked system, which is reversible (Write category) and affects project documentation and team workflows. High severity reflects the potential for an agent to incorrectly update critical bug information, mislead teams on issue status, or corrupt project records.

From the tool's definition Tool name 'update_bug' indicates modification of bug records in an agile project management system (TAPD). The server manages 'defects' and provides 'API access tokens', indicating persistent data changes.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_bug Rate-limited

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

FAQ

Questions about update_bug

What does the update_bug tool do? +

update_bug. It is categorised as a Write tool in the TAPD 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 update_bug? +

Register the TAPD MCP Server MCP server in PolicyLayer and add a rule for update_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 TAPD MCP Server. Nothing to install.

What risk level is update_bug? +

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

Can I rate-limit update_bug? +

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

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

update_bug is provided by the TAPD MCP Server MCP server (ken19990709/mcp-server-for-tapd). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.