search_test_cases
AI agents call search_test_cases to retrieve information from TestRail MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Search operations retrieve and query data without modifying, deleting, or executing code. The name strongly suggests a read-only retrieval function. Confidence is moderate-high because the description is empty, but the tool name and server context leave little ambiguity about its read-only nature. No severity beyond low since it cannot cause data modification or trigger external operations.
From the tool's definition Tool name is 'search_test_cases' which indicates a query/search operation. The server context describes managing test cases in TestRail, and search operations are retrieval-only without side effects.
Attacks that exploit this kind of access
search_test_cases. It is categorised as a Read tool in the TestRail MCP Server MCP Server, which means it retrieves data without modifying state.
Register the TestRail MCP Server MCP server in PolicyLayer and add a rule for search_test_cases: 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 TestRail MCP Server. Nothing to install.
search_test_cases 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_test_cases 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_test_cases. 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_test_cases is provided by the TestRail MCP Server MCP server (trtmn/tram-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 →