AI agents use createPullRequestTask to create or update resources in Bitbucket MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bitbucket MCP environment.
This tool creates a new task artifact within a pull request, modifying the PR's state and content. Creation is reversible (tasks can be deleted, as evidenced by the sibling tool 'deletePullRequestTask'), so this is a Write operation rather than Destructive. Severity is medium because misuse could create spam tasks or mislead reviewers, but the impact is limited to a single PR and easily correctable.
From the tool's definition Tool name 'createPullRequestTask' and description 'Create a task on a pull request' indicate creation of new data (a task) on a PR, which is a reversible modification.
Documented attack patterns abuse exactly the kind of access createPullRequestTask gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Bitbucket MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for createPullRequestTask:
{
"version": "1",
"default": "deny",
"tools": {
"createPullRequestTask": {
"limits": [
{
"counter": "createpullrequesttask_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}createPullRequestTask stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a task on a pull request. It is categorised as a Write tool in the Bitbucket MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Bitbucket MCP server in PolicyLayer and add a rule for createPullRequestTask: 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 MCP. Nothing to install.
createPullRequestTask is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the createPullRequestTask 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 createPullRequestTask. 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.
createPullRequestTask is provided by the Bitbucket MCP server (matanyemini/bitbucket-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Bitbucket MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
49 Bitbucket MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.