AI agents call list_jira_issues to retrieve information from Atlassian without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Listing issues is a read-only operation that retrieves data from Jira without modifying, deleting, or executing actions. The blast radius of misuse is minimal—an agent could retrieve unwanted information but cannot alter state, execute operations, or cause financial impact. The empty description slightly reduces confidence, but the tool name and server context are clear enough to classify with reasonable confidence.
From the tool's definition Tool name 'list_jira_issues' indicates a listing/querying operation. The server description states it enables LLMs to 'search, read, write, and manage issues', and this tool's name clearly aligns with the read/search capability.
Attacks that exploit this kind of access
list_jira_issues. It is categorised as a Read tool in the Atlassian MCP Server, which means it retrieves data without modifying state.
Register the Atlassian MCP server in PolicyLayer and add a rule for list_jira_issues: 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 Atlassian. Nothing to install.
list_jira_issues 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 list_jira_issues 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 list_jira_issues. 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.
list_jira_issues is provided by the Atlassian MCP server (tingyiy/atlassian-mcp-server). 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 →