log_change

Log a code change to the persistent change ledger. Models MUST call this after modifying files. Enables cross-session coherence.

SERVERMcp Dev SOURCE2loch-ness6/mempalace-mcp-dev

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/2loch-ness6-mempalace-mcp-dev/log-change.md

WHAT IT DOES

What log_change does on Mcp Dev

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

RISK

Why log_change is rated Medium

This tool writes entries to a persistent change ledger. It creates/appends records rather than modifying code directly, and the action is reversible (log entries could be removed). It is not destructive, financial, or executable in the code-execution sense. Severity is medium because a misused or spammed log could corrupt cross-session coherence and mislead the AI about the state of the codebase.

From the tool's definition 'Log a code change to the persistent change ledger' and 'Models MUST call this after modifying files'

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs log_change safely

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

log_change Rate-limited

log_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": {
    "log_change": {
      "limits": [
        {
          "counter": "log_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 Dev, apply this rule, and every log_change call is checked against it from then on.

FAQ

Questions about log_change

What does the log_change tool do? +

Log a code change to the persistent change ledger. Models MUST call this after modifying files. Enables cross-session coherence. It is categorised as a Write tool in the Mcp Dev MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on log_change? +

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

What risk level is log_change? +

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

Can I rate-limit log_change? +

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

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

log_change is provided by the Mcp Dev MCP server (2loch-ness6/mempalace-mcp-dev). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Dev, and thousands of servers like it.

This server

All 19 Mcp Dev tools →

Across the catalogue

The MCP Attack Database →

Guides

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