get_issue_sla
AI agents call get_issue_sla 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 SLA data from Jira issues without modifying or deleting anything. SLA metrics are informational metadata. The blast radius of misuse is minimal—an agent could at worst spam queries or retrieve sensitive timeline information, but cannot alter systems or cause financial harm. Low severity is appropriate for an informational read operation.
From the tool's definition Tool name 'get_issue_sla' indicates retrieval of SLA (Service Level Agreement) information associated with a Jira issue. The 'get_' prefix and absence of modification/deletion language strongly suggest a read-only query operation.
Attacks that exploit this kind of access
get_issue_sla. 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_issue_sla: 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_issue_sla 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_issue_sla 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_issue_sla. 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_issue_sla is provided by the MCP Atlassian MCP server (lklkxcxc/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 →