AI agents call search_aio_testcase 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 performs a search operation to retrieve test cases based on filtering criteria (project and/or folders). It has no side effects, does not modify data, execute code, or trigger external operations. It is purely a data retrieval function, fitting squarely within the Read category. The low severity reflects minimal blast radius—misuse would only expose test case metadata.
From the tool's definition Tool name 'search_aio_testcase' and description 'Search test cases by project and/or folders' indicate retrieval/query operations with no modification or execution of external code.
Attacks that exploit this kind of access
Search test cases by project and/or folders. 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 search_aio_testcase: 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.
search_aio_testcase 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 search_aio_testcase 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 search_aio_testcase. 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.
search_aio_testcase 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 →