Get list of all accessible Jira projects
AI agents call jira_get_projects to retrieve information from Jira MCP Integration without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves project metadata from Jira without modifying, deleting, or executing any operations. It is a read-only query that returns project information. Even if misused by an AI agent, the only risk is information disclosure about accessible projects, which is low severity. No side effects or irreversible actions are possible.
From the tool's definition Tool description explicitly states 'Get list of all accessible Jira projects' - a retrieval operation with no modification or deletion capabilities. The verb 'Get' and the scope 'list of projects' indicate a simple query operation.
Attacks that exploit this kind of access
Get list of all accessible Jira projects. It is categorised as a Read tool in the Jira MCP Integration MCP Server, which means it retrieves data without modifying state.
Register the Jira MCP Integration MCP server in PolicyLayer and add a rule for jira_get_projects: 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 MCP Integration. Nothing to install.
jira_get_projects 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_projects 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_projects. 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_projects is provided by the Jira MCP Integration MCP server (koveh/jira-mcp). 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 →