AI agents use reopenComment 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 modifies data (comment thread status) in a reversible manner. Reopening a comment can be undone by resolving it again. It does not delete, destroy, or execute code. It falls squarely into the Write category. Severity is low because the blast radius is minimal—changing comment thread states on PRs has no cascading effects on the codebase, deployments, or other critical systems.
From the tool's definition Tool description states 'Reopen a resolved comment thread on a pull request', which modifies the state of a comment from resolved to reopened. This is a state change that reverses a previous action (resolving the comment).
Documented attack patterns abuse exactly the kind of access reopenComment 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 reopenComment:
{
"version": "1",
"default": "deny",
"tools": {
"reopenComment": {
"limits": [
{
"counter": "reopencomment_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}reopenComment 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.
Reopen a resolved comment thread 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 reopenComment: 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.
reopenComment 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 reopenComment 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 reopenComment. 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.
reopenComment 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.