get_changed_files

List files changed since a base ref (default: HEAD~1). Useful to understand scope of recent changes.

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-changed-files.md

WHAT IT DOES

What get_changed_files does on Mcp Dev

AI agents call get_changed_files 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_changed_files is rated Low

This tool retrieves metadata about file changes in git history. It has no side effects, does not execute code, does not modify or delete data, and does not perform financial operations. It is purely informational, similar to running 'git diff --name-only'. The blast radius of misuse is minimal — an attacker could only learn which files have changed, which is low-sensitivity metadata in most contexts.

From the tool's definition Tool name is 'get_changed_files' and description states 'List files changed since a base ref' — this is a query/retrieval operation that reports on git history without modifying any data.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_changed_files Allowed

get_changed_files 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_changed_files": {}
  }
}

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_changed_files call is checked against it from then on.

FAQ

Questions about get_changed_files

What does the get_changed_files tool do? +

List files changed since a base ref (default: HEAD~1). Useful to understand scope of recent changes. 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_changed_files? +

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

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

Can I rate-limit get_changed_files? +

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

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

get_changed_files 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

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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