Create a new issue in a Bitbucket repository (requires issue tracker to be enabled)
AI agents use bitbucket_create_issue to create or update resources in Sage MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sage MCP environment.
This tool creates a new issue (ticket) in Bitbucket, which is a write operation that modifies repository state by adding data. It is reversible—issues can be deleted or closed—so it does not qualify as Destructive.
From the tool's definition Tool name contains 'create' and description states 'Create a new issue in a Bitbucket repository', which is a reversible data creation operation.
Documented attack patterns abuse exactly the kind of access bitbucket_create_issue gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Sage MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for bitbucket_create_issue:
{
"version": "1",
"default": "deny",
"tools": {
"bitbucket_create_issue": {
"limits": [
{
"counter": "bitbucket_create_issue_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}bitbucket_create_issue 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 new issue in a Bitbucket repository (requires issue tracker to be enabled). It is categorised as a Write tool in the Sage MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sage MCP server in PolicyLayer and add a rule for bitbucket_create_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.
bitbucket_create_issue 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 bitbucket_create_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.
Set action: deny in the PolicyLayer policy for bitbucket_create_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.
bitbucket_create_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.
Deterministic rules across all 359 Sage MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
359 Sage MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.