Get the last editor of a file from Git history
AI agents call get_file_last_editor to retrieve information from MCP Memory Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries Git history to retrieve information about who last edited a file. It has no side effects, does not create, modify, delete, or execute any operations. It is a straightforward data retrieval operation that fits the Read category. The severity is low because exposing git history metadata poses minimal risk—it cannot be exploited to compromise systems or data integrity.
From the tool's definition Tool name 'get_file_last_editor' and description 'Get the last editor of a file from Git history' indicate a read-only query operation that retrieves metadata about file history without modifying anything.
Attacks that exploit this kind of access
Get the last editor of a file from Git history. It is categorised as a Read tool in the MCP Memory Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Memory Server MCP server in PolicyLayer and add a rule for get_file_last_editor: 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.
get_file_last_editor 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_file_last_editor 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_file_last_editor. 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_file_last_editor 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.
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 →