Set the default Atlassian account used when no site hint is given
AI agents use set_default_atlassian_account to create or update resources in Atlassian Multi — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Atlassian Multi environment.
This tool writes a configuration preference (default account selection) but creates no new data and causes no side effects beyond affecting future routing behavior. It is reversible—the default can be changed again. It does not delete data, execute arbitrary operations, or move funds.
From the tool's definition Tool description states it 'Set the default Atlassian account', which modifies configuration state. The word 'set' indicates modification of a user preference/setting.
Attacks that exploit this kind of access
Set the default Atlassian account used when no site hint is given. It is categorised as a Write tool in the Atlassian Multi MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Atlassian Multi MCP server in PolicyLayer and add a rule for set_default_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.
set_default_atlassian_account 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 set_default_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 set_default_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.
set_default_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 →