get_all_changes

Get all changes in the ledger, optionally filtered by ISO timestamp.

SERVERMcp Dev SOURCE2loch-ness6/mempalace-mcp-dev

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/2loch-ness6-mempalace-mcp-dev/get-all-changes.md

WHAT IT DOES

What get_all_changes does on Mcp Dev

AI agents call get_all_changes to retrieve information from Mcp Dev without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_all_changes is rated Low

This tool retrieves and queries a change ledger with optional filtering. It has no side effects—it does not create, modify, delete, execute code, or trigger external operations. It is a straightforward data retrieval operation, consistent with the 'Read' category. Severity is low because access to change history poses minimal risk even if misused by an AI agent.

From the tool's definition Tool name 'get_all_changes' and description 'Get all changes in the ledger, optionally filtered by ISO timestamp' indicate a read-only query operation that retrieves historical change data without modifying or executing anything.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_all_changes 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 get_all_changes, this is the rule to start with:

get_all_changes Allowed

get_all_changes is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_all_changes": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about get_all_changes

What does the get_all_changes tool do? +

Get all changes in the ledger, optionally filtered by ISO timestamp. It is categorised as a Read tool in the Mcp Dev MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_all_changes? +

Register the Mcp Dev MCP server in PolicyLayer and add a rule for get_all_changes: 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 get_all_changes? +

get_all_changes is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_all_changes? +

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

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

get_all_changes 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

review_changes on MCP Server PR Pilot →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →