Get all issues for a specific project. Returns issues ordered by creation date.
AI agents call jira_get_project_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.
This tool queries and retrieves existing Jira issues without modifying, deleting, or executing any actions. It is a straightforward data retrieval operation that fits the Read category. Severity is low because unauthorized access to issue lists presents minimal risk compared to Write, Execute, or Destructive operations, though the actual risk depends on the sensitivity of project data contained in those issues.
From the tool's definition Tool name 'jira_get_project_issues' and description 'Get all issues for a specific project. Returns issues ordered by creation date.' indicate a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access jira_get_project_issues gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Atlassian, and nothing reaches the server without passing your rules. This is the rule we recommend for jira_get_project_issues:
{
"version": "1",
"default": "deny",
"tools": {
"jira_get_project_issues": {}
}
}jira_get_project_issues is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get all issues for a specific project. Returns issues ordered by creation date. 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 jira_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 Atlassian. Nothing to install.
jira_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 jira_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 jira_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.
jira_get_project_issues is provided by the Atlassian MCP server (xuanxt/atlassian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Atlassian, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
51 Atlassian tools catalogued and risk-classified — across an index of 43,000+ MCP servers.