update_bug · Follow Plan MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_bug does on Follow Plan MCP Server

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

WHY IT NEEDS A POLICY

Why update_bug needs a policy

This tool modifies existing bug records in the tracking system. While updates are reversible (can be corrected with subsequent updates), the tool could be misused to alter bug severity, status, or description in ways that mislead stakeholders or hide issues. The medium severity reflects a bounded blast radius limited to a single bug record; however, widespread misuse could damage project transparency.

From the tool's definition Tool name 'update_bug' and description 'Update an existing bug' indicate modification of existing data. The context shows this is a project management system with bug tracking that uses SQLite persistence.

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 Follow Plan MCP Server, so you can run agents against it safely.

FAQ

Questions about update_bug

What does the update_bug tool do? +

Update an existing bug. It is categorised as a Write tool in the Follow Plan 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 Follow Plan 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 Follow Plan 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 Follow Plan MCP Server MCP server (vibeclasses/follow-plan-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.