Test connection and credentials for a configured Atlassian account
AI agents call test_atlassian_connection to retrieve information from Atlassian Multi without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a connection verification and credential validation check. These are non-destructive, non-modifying operations that query the status of an existing account configuration. No data is created, modified, deleted, or executed. The tool has minimal blast radius—worst case, it reveals that an account is or isn't configured, but does not alter any Jira or Confluence resources.
From the tool's definition Tool is named 'test_atlassian_connection' and described as 'Test connection and credentials for a configured Atlassian account'. The verb 'test' indicates a read-only diagnostic operation that verifies connectivity without modifying or creating any data.
Attacks that exploit this kind of access
Test connection and credentials for a configured Atlassian account. It is categorised as a Read tool in the Atlassian Multi MCP Server, which means it retrieves data without modifying state.
Register the Atlassian Multi MCP server in PolicyLayer and add a rule for test_atlassian_connection: 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.
test_atlassian_connection is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the test_atlassian_connection 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 test_atlassian_connection. 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.
test_atlassian_connection 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 →