log_change · Coord MCP: Risk & Policy

WHAT IT DOES

What log_change does on CoordMCP

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

WHY IT NEEDS A POLICY

Why log_change needs a policy

Based on the tool name alone, 'log_change' most likely records or writes a change entry to shared memory or a change log, consistent with the server's purpose of tracking decisions and maintaining consistency. This is a Write operation (creating/appending a log record). Severity is medium given it operates in a multi-agent coordination context where incorrect log entries could mislead other agents.

From the tool's definition Tool name 'log_change' — description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

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.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches CoordMCP, so you can run agents against it safely.

FAQ

Questions about log_change

What does the log_change tool do? +

log_change. It is categorised as a Write tool in the CoordMCP 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 Coord 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 CoordMCP. 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 Coord MCP server (siddiquesahabaj/coordmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.