get_user_profile
AI agents call get_user_profile to retrieve information from MCP Atlassian without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool's name strongly suggests it retrieves user profile information (a query/fetch operation) rather than creating, modifying, or deleting data. No side effects or state changes are implied. While the empty description reduces confidence slightly, the naming convention and context within a read-heavy Atlassian integration server support Read classification.
From the tool's definition Tool name 'get_user_profile' indicates a retrieval operation that queries user profile data. The description is empty, but the name and context (integration with Atlassian products for 'searching content' and 'managing issues') suggest this reads user…
Attacks that exploit this kind of access
get_user_profile. It is categorised as a Read tool in the MCP Atlassian MCP Server, which means it retrieves data without modifying state.
Register the MCP Atlassian MCP server in PolicyLayer and add a rule for get_user_profile: 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 MCP Atlassian. Nothing to install.
get_user_profile 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 get_user_profile 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 get_user_profile. 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.
get_user_profile is provided by the MCP Atlassian MCP server (thienntdev/mcp-atlassian). 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 →