Retrieve all Jira projects accessible to the authenticated user. Returns project keys, names, IDs, and basic metadata. Use this to discover available projects before creating issues or performing other operations.
AI agents call get_projects to retrieve information from Raalarcon Jira without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a query that retrieves and returns project metadata without modifying, executing external operations, or deleting anything. It has no side effects and is explicitly a discovery/retrieval function. The blast radius is minimal—an agent learning what projects exist poses no meaningful risk.
From the tool's definition Tool name is 'get_projects' and description states 'Retrieve all Jira projects accessible to the authenticated user' with 'Returns project keys, names, IDs, and basic metadata.' The verbs 'Retrieve' and 'Returns' indicate a read-only query operation.
Attacks that exploit this kind of access
Retrieve all Jira projects accessible to the authenticated user. Returns project keys, names, IDs, and basic metadata. Use this to discover available projects before creating issues or performing other operations. It is categorised as a Read tool in the Raalarcon Jira MCP Server, which means it retrieves data without modifying state.
Register the Raalarcon Jira MCP server in PolicyLayer and add a rule for 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 Raalarcon Jira. Nothing to install.
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 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 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.
get_projects is provided by the Raalarcon Jira MCP server (raalarcon-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 →