get_commit_diff
AI agents call get_commit_diff to retrieve information from Bitbucket Server MCP 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 the differences between commits—a non-destructive, informational operation with no side effects. It fits the Read category (retrieves or queries data). Low severity because viewing diffs poses minimal security risk even if misused by an agent. High confidence despite empty description because the name unambiguously indicates a read operation.
From the tool's definition Tool name 'get_commit_diff' indicates retrieval of commit differences/changes. The verb 'get' is characteristic of read operations that query data without modification. No description provided, but name strongly suggests data retrieval.
Attacks that exploit this kind of access
get_commit_diff. It is categorised as a Read tool in the Bitbucket Server MCP MCP Server, which means it retrieves data without modifying state.
Register the Bitbucket Server MCP server in PolicyLayer and add a rule for get_commit_diff: 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 Bitbucket Server MCP. Nothing to install.
get_commit_diff 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_diff 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_diff. 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_diff is provided by the Bitbucket Server MCP server (manpreetshuann/bitbucket-server-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 →