get_project_issues
AI agents call get_project_issues 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 and retrieves issue data from a Jira project. It has no side effects, does not modify data, and does not execute external operations. The blast radius of misuse is minimal — an agent could retrieve sensitive issue information, but cannot delete, modify, or execute actions. Low severity due to the read-only nature and the fact that Jira permissions would typically control what issues are visible.
From the tool's definition Tool name is 'get_project_issues' which is a retrieval operation. The sibling tools on this server include 'get_agile_boards', 'get_all_projects', 'get_comments', and 'download_attachment' — all Read operations.
Attacks that exploit this kind of access
get_project_issues. 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_project_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 MCP Atlassian. Nothing to install.
get_project_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 get_project_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 get_project_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.
get_project_issues 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.