AI agents call get_aio_projects to retrieve information from Jira Aio without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves a list of projects from the Jira AIO Test Case Management System. It is a read-only operation that queries existing data without creating, modifying, deleting, or executing any actions. The severity is low because unauthorized access to a project list, while potentially revealing organizational structure, does not directly compromise data integrity or enable financial harm.
From the tool's definition Tool name 'get_aio_projects' and description 'Get list of all projects in AIO' indicate a retrieval operation. The verb 'Get' and the lack of any modification, deletion, or execution keywords confirm this is a data retrieval function with no side effects.
Attacks that exploit this kind of access
Get list of all projects in AIO. It is categorised as a Read tool in the Jira Aio MCP Server, which means it retrieves data without modifying state.
Register the Jira Aio MCP server in PolicyLayer and add a rule for get_aio_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 Aio. Nothing to install.
get_aio_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_aio_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_aio_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_aio_projects is provided by the Jira Aio MCP server (qamary666/jira-aio-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 →