Show recent git commit log (one line each).
AI agents call git_log to retrieve information from Cursor MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays historical git commit information. It does not modify, delete, or execute code—it only queries and presents existing data from the git repository's commit log. This is a classic Read operation with minimal risk, suitable for code browsing and understanding version control history.
From the tool's definition Tool name 'git_log' and description 'Show recent git commit log (one line each)' indicate a read-only query of version control history with no side effects.
Attacks that exploit this kind of access
Show recent git commit log (one line each). It is categorised as a Read tool in the Cursor MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Cursor MCP Server MCP server in PolicyLayer and add a rule for git_log: 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 Cursor MCP Server. Nothing to install.
git_log 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 git_log 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 git_log. 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.
git_log is provided by the Cursor MCP Server MCP server (tariqnasheed/cursor_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 →