AI agents call get_project_issues to retrieve information from Jira 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 issue data from a Jira project without any side effects. It performs a read-only operation that does not create, modify, delete, or trigger any external actions. The blast radius of misuse is minimal — an agent could retrieve sensitive issue information but cannot alter system state or data.
From the tool's definition Tool name is 'get_project_issues' and description states 'Get all issues for a specific project' — a straightforward data retrieval operation with no modification, deletion, or execution of external commands.
Attacks that exploit this kind of access
Get all issues for a specific project. It is categorised as a Read tool in the Jira MCP Server, which means it retrieves data without modifying state.
Register the Jira 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 Jira. 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 Jira MCP server (taraskhust/jira-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 →