최근 커밋 히스토리를 조회합니다
AI agents call get_commit_history to retrieve information from Remote Memory MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves commit history from a repository—a non-destructive, non-modifying data retrieval operation. It has no side effects on the knowledge graph or repository state. The low severity reflects minimal blast radius: misuse would only expose historical metadata already stored in the repository.
From the tool's definition Tool name is 'get_commit_history' and description translates to 'Retrieves recent commit history'. The verb 'get' and 'retrieve' indicate a read-only query operation that accesses historical data without modification.
Attacks that exploit this kind of access
최근 커밋 히스토리를 조회합니다. It is categorised as a Read tool in the Remote Memory MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Remote Memory MCP Server MCP server in PolicyLayer and add a rule for get_commit_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 Remote Memory MCP Server. Nothing to install.
get_commit_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_commit_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_commit_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_commit_history is provided by the Remote Memory MCP Server MCP server (yeomyujun/remote-memory-mcp-server). 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 →