record_change

Record a durable change event after code, config, or infrastructure changes.

SERVERMcp Control Plane SOURCEalbertik322-sudo/mcp-control-plane

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mcp-control-plane/record-change.md

WHAT IT DOES

What record_change does on Mcp Control Plane

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

RISK

Why record_change is rated Medium

This tool writes/persists a change event record to some durable store. It creates new data (an audit/change log entry) but does not delete or irreversibly modify existing data. It is a Write operation with medium severity since misuse could pollute change logs or audit trails, but it does not directly destroy data or trigger destructive operations.

From the tool's definition Record a durable change event after code, config, or infrastructure changes

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs record_change safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Control Plane, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For record_change, this is the rule to start with:

record_change Rate-limited

record_change 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": {
    "record_change": {
      "limits": [
        {
          "counter": "record_change_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Control Plane, apply this rule, and every record_change call is checked against it from then on.

FAQ

Questions about record_change

What does the record_change tool do? +

Record a durable change event after code, config, or infrastructure changes. It is categorised as a Write tool in the Mcp Control Plane MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on record_change? +

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

What risk level is record_change? +

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

Can I rate-limit record_change? +

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

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

record_change is provided by the Mcp Control Plane MCP server (albertik322-sudo/mcp-control-plane). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Control Plane, and thousands of servers like it.

This server

All 286 Mcp Control Plane tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_record_checkpoint on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →