Get worklog entries for a Jira issue.
AI agents call get_worklog 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 queries worklog data from Jira issues without creating, modifying, or deleting any information. It has no side effects and presents minimal security risk. The data retrieved (time tracking entries) is typically non-sensitive operational information already visible to authorized Jira users. Misuse would result only in information disclosure within existing access boundaries.
From the tool's definition Tool name 'get_worklog' and description 'Get worklog entries for a Jira issue' indicate a retrieval operation with no modification capability. The verb 'Get' and the absence of any update or deletion language confirm read-only behavior.
Attacks that exploit this kind of access
Get worklog entries for a Jira issue. 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_worklog: 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_worklog 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_worklog 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_worklog. 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_worklog is provided by the MCP Atlassian MCP server (uchinx/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 →