add_changelog_entry · MCP Memory Server MCP: Risk & Policy

WHAT IT DOES

What add_changelog_entry does on MCP Memory Server

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

WHY IT NEEDS A POLICY

Why add_changelog_entry needs a policy

This tool creates or modifies changelog records, which is a write operation. While it modifies project state, the modification is intended to be reversible and non-destructive. The blast radius is medium because malicious changelog entries could mislead developers about project history or mask unauthorized changes, but the tool does not directly execute code, delete critical data, or move financial resources.

From the tool's definition Tool name 'add_changelog_entry' and description 'Add an entry to the project changelog' indicate creation/modification of changelog data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_changelog_entry Rate-limited

add_changelog_entry 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": {
    "add_changelog_entry": {
      "limits": [
        {
          "counter": "add_changelog_entry_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 MCP Memory Server, so you can run agents against it safely.

FAQ

Questions about add_changelog_entry

What does the add_changelog_entry tool do? +

Add an entry to the project changelog. It is categorised as a Write tool in the MCP Memory 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 add_changelog_entry? +

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

What risk level is add_changelog_entry? +

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

Can I rate-limit add_changelog_entry? +

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

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

add_changelog_entry is provided by the MCP Memory Server MCP server (keleshteri/mcp-memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.