convert_to_draft
AI agents use convert_to_draft to create or update resources in Bitbucket Server MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bitbucket Server MCP environment.
Converting a pull request to draft status changes its metadata and visibility state but does not delete data or execute arbitrary code. This is a reversible modification operation, placing it in the Write category. Severity is medium because misuse could confuse code review workflows, but the action is undoable.
From the tool's definition Tool named 'convert_to_draft' with empty description; sibling tools on this server include 'create_draft_pull_request' and operations on pull requests. The name suggests converting an existing pull request to draft status, which modifies state reversibly.
Attacks that exploit this kind of access
convert_to_draft. It is categorised as a Write tool in the Bitbucket Server MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Bitbucket Server MCP server in PolicyLayer and add a rule for convert_to_draft: 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.
convert_to_draft 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 convert_to_draft 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 convert_to_draft. 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.
convert_to_draft 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 →