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 retrieves (gets) worklog entries from a Jira issue, which is a read-only query operation. It has no side effects—it does not create, modify, delete, or execute any actions. The blast radius of misuse is minimal, as an attacker could only view time tracking information already recorded in the system.
From the tool's definition Tool name 'get_worklog' and description 'Get worklog entries for a Jira issue' indicate retrieval of existing time tracking data without modification or deletion.
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 (sooperset/mcp-atlassian). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.