Get the history of file edits
AI agents call get_edit_history to retrieve information from MCP Start App without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical information about file edits—a read-only operation with no side effects. It queries past edit data without creating, modifying, deleting, or executing any operations. The low severity reflects minimal risk; an AI agent misusing this tool could only access edit history metadata, not modify files or system state.
From the tool's definition Tool name 'get_edit_history' and description 'Get the history of file edits' indicate a retrieval operation with no modification or execution capability.
Attacks that exploit this kind of access
Get the history of file edits. It is categorised as a Read tool in the MCP Start App MCP Server, which means it retrieves data without modifying state.
Register the MCP Start App MCP server in PolicyLayer and add a rule for get_edit_history: 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 Start App. Nothing to install.
get_edit_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_edit_history 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.
Set action: deny in the PolicyLayer policy for get_edit_history. 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.
get_edit_history is provided by the MCP Start App MCP server (nexus-aissam/mcp-local). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →