Get current user info for a configured account
AI agents call atlassianUserInfo 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 retrieves user information for an authenticated account without creating, modifying, deleting, executing code, or moving money. It is a straightforward read operation. The low severity reflects minimal blast radius—user info retrieval is generally non-sensitive in most contexts, though exposure could leak identity details depending on what 'user info' includes.
From the tool's definition Tool name 'atlassianUserInfo' and description 'Get current user info for a configured account' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get current user info for a configured 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 atlassianUserInfo: 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.
atlassianUserInfo 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 atlassianUserInfo 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 atlassianUserInfo. 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.
atlassianUserInfo 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 →