Remove a configured Atlassian account
AI agents call remove_atlassian_account to permanently remove resources in Atlassian Multi — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool removes (deletes) a configured account, which cannot be undone—a hallmark of Destructive category. While not directly data-destructive, account removal is an irreversible configuration change that severs all future integration with that workspace. An AI agent removing wrong accounts could disable critical Jira/Confluence access.
From the tool's definition Tool name 'remove_atlassian_account' and description 'Remove a configured Atlassian account' indicate irreversible deletion of account configuration.
Attacks that exploit this kind of access
Remove a configured Atlassian account. It is categorised as a Destructive tool in the Atlassian Multi MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Atlassian Multi MCP server in PolicyLayer and add a rule for remove_atlassian_account: 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 Atlassian Multi. Nothing to install.
remove_atlassian_account is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_atlassian_account 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 remove_atlassian_account. 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.
remove_atlassian_account is provided by the Atlassian Multi MCP server (ntlongctt/atlassian-multi-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 →