Retrieves recent git commits for the workspace. Useful for correlating code changes
AI agents call get_recent_commits to retrieve information from Debugging MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only operation that queries version control history. It retrieves historical information about code changes without modifying any data, executing code, or triggering side effects. The tool is informational in nature, consistent with the 'search, list, get, fetch' pattern of the Read category.
From the tool's definition Tool retrieves recent git commits; described as retrieving/reading data ('Retrieves recent git commits'). No modification, deletion, or execution is performed.
Attacks that exploit this kind of access
Retrieves recent git commits for the workspace. Useful for correlating code changes. It is categorised as a Read tool in the Debugging MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Debugging MCP Server MCP server in PolicyLayer and add a rule for get_recent_commits: 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 Debugging MCP Server. Nothing to install.
get_recent_commits 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_recent_commits 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_recent_commits. 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_recent_commits is provided by the Debugging MCP Server MCP server (luischang07/debugging-mcp). 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 →