Get a stream of recent user activity, such as issue comments, status changes, and field updates. Can filter by activity type and project.
AI agents call get_user_activity_history 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.
This tool retrieves historical activity logs and audit information from Jira/Confluence. While it is a Read operation with no side effects, the severity is medium rather than low because activity history can contain sensitive information about user behavior, project decisions, and system changes.
From the tool's definition Tool description states 'Get a stream of recent user activity' - the verb 'Get' indicates data retrieval with no modification. Activity types (comments, status changes, field updates) are being queried, not created or deleted.
Attacks that exploit this kind of access
Get a stream of recent user activity, such as issue comments, status changes, and field updates. Can filter by activity type and project. 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_activity_history: 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_activity_history 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_activity_history 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_activity_history. 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_activity_history is provided by the Mcp Atlassian MCP server (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 →