bitbucket_get_issue

Get details of a specific issue

SERVERSage MCP SOURCEsagemcp/sagemcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sagemcp-sagemcp/bitbucket-get-issue.md

WHAT IT DOES

What bitbucket_get_issue does on Sage MCP

AI agents call bitbucket_get_issue to retrieve information from Sage MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why bitbucket_get_issue is rated Low

This tool retrieves information about a Bitbucket issue. The 'get' verb and 'Get details' language indicate a read-only operation that queries existing data. There are no side effects, no modifications, no code execution, and no data deletion. The blast radius is minimal—misuse would only expose issue details the authenticated user is already authorized to access.

From the tool's definition Tool name includes 'get' and description states 'Get details of a specific issue' — a query operation that retrieves data without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs bitbucket_get_issue safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Sage MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bitbucket_get_issue, this is the rule to start with:

bitbucket_get_issue Allowed

bitbucket_get_issue is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "bitbucket_get_issue": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Sage MCP, apply this rule, and every bitbucket_get_issue call is checked against it from then on.

FAQ

Questions about bitbucket_get_issue

What does the bitbucket_get_issue tool do? +

Get details of a specific issue. It is categorised as a Read tool in the Sage MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on bitbucket_get_issue? +

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

What risk level is bitbucket_get_issue? +

bitbucket_get_issue is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit bitbucket_get_issue? +

Yes. Add a rate_limit block to the bitbucket_get_issue 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_get_issue completely? +

Set action: deny in the PolicyLayer policy for bitbucket_get_issue. 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_get_issue? +

bitbucket_get_issue is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Sage, and thousands of servers like it.

This server

All 359 Sage tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →