Gets a list of all changed files in a pull request with file-level metadata (file paths, change types like ADD/MODIFY/DELETE, content IDs). This is useful for getting an overview of what files changed. For line-by-line diff data, use get_pull_request_file_diff.
AI agents call get_pull_request_changes to retrieve information from Mcp Bitbucket 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 queries pull request metadata about file changes. It does not create, modify, delete, execute, or move anything—it only fetches information about what files changed in a pull request. This is a pure read operation with no side effects, making it the lowest severity classification.
From the tool's definition Tool description states it 'Gets a list of all changed files' and provides 'file-level metadata' including 'file paths, change types'. The verb 'Gets' and the read-only nature of retrieving metadata about changes indicates no side effects or modifications.
Attacks that exploit this kind of access
Gets a list of all changed files in a pull request with file-level metadata (file paths, change types like ADD/MODIFY/DELETE, content IDs). This is useful for getting an overview of what files changed. For line-by-line diff data, use get_pull_request_file_diff. It is categorised as a Read tool in the Mcp Bitbucket Server MCP Server, which means it retrieves data without modifying state.
Register the Mcp Bitbucket Server MCP server in PolicyLayer and add a rule for get_pull_request_changes: 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 Bitbucket Server. Nothing to install.
get_pull_request_changes 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_pull_request_changes 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_pull_request_changes. 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_pull_request_changes is provided by the Mcp Bitbucket Server MCP server (mcp-bitbucket-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 →