bitbucket_pr_comments · ContextForge MCP Gateway MCP

WHAT IT DOES

What bitbucket_pr_comments does on ContextForge MCP Gateway

AI agents use bitbucket_pr_comments to create or update resources in ContextForge MCP Gateway — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ContextForge MCP Gateway environment.

WHY IT NEEDS A POLICY

Why bitbucket_pr_comments needs a policy

The tool performs both read (list) and write (add) operations. The write capability—adding comments—creates new data that modifies the pull request state reversibly. This is a Write category tool rather than Read because the primary documented function includes data creation.

From the tool's definition Tool description states it can 'add comments on a pull request', which is a write operation that creates new data (comments) on a code review artifact.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

bitbucket_pr_comments Rate-limited

bitbucket_pr_comments 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "bitbucket_pr_comments": {
      "limits": [
        {
          "counter": "bitbucket_pr_comments_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches ContextForge MCP Gateway, so you can run agents against it safely.

FAQ

Questions about bitbucket_pr_comments

What does the bitbucket_pr_comments tool do? +

List or add comments on a pull request. It is categorised as a Write tool in the ContextForge MCP Gateway MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on bitbucket_pr_comments? +

Register the ContextForge MCP Gateway MCP server in PolicyLayer and add a rule for bitbucket_pr_comments: 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 ContextForge MCP Gateway. Nothing to install.

What risk level is bitbucket_pr_comments? +

bitbucket_pr_comments is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit bitbucket_pr_comments? +

Yes. Add a rate_limit block to the bitbucket_pr_comments 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.

How do I block bitbucket_pr_comments completely? +

Set action: deny in the PolicyLayer policy for bitbucket_pr_comments. 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.

What MCP server provides bitbucket_pr_comments? +

bitbucket_pr_comments is provided by the ContextForge MCP Gateway MCP server (jrmatherly/mcp-context-forge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

bitbucket_pr_comments is one line of ContextForge MCP Gateway's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →