register_plan · Codeviewer MCP: Risk & Policy

WHAT IT DOES

What register_plan does on Codeviewer

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

WHY IT NEEDS A POLICY

Why register_plan needs a policy

The 'register' verb combined with 'execution plan' indicates the tool creates or stores a new plan record in the server's session state. This is a reversible write operation (plans can presumably be cleaned up via cleanup_session). It does not delete data (not Destructive), execute arbitrary code (not Execute), involve finances (not Financial), or merely read data (not Read).

From the tool's definition Tool description states 'Register an execution plan' which involves creating/storing a new plan object in the system's state. The server is described as 'stateful' with 'iterative review sessions', indicating this tool persists data structures.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

register_plan Rate-limited

register_plan 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": {
    "register_plan": {
      "limits": [
        {
          "counter": "register_plan_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 Codeviewer, so you can run agents against it safely.

FAQ

Questions about register_plan

What does the register_plan tool do? +

Register an execution plan for iterative MCP code review. It is categorised as a Write tool in the Codeviewer MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on register_plan? +

Register the Codeviewer MCP server in PolicyLayer and add a rule for register_plan: 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 Codeviewer. Nothing to install.

What risk level is register_plan? +

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

Can I rate-limit register_plan? +

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

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

register_plan is provided by the Codeviewer MCP server (master0ffate/codeviewer-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.