Search for test cases in a specific folder
AI agents call search_test_cases_by_folder to retrieve information from Zephyr Scale MCP Server 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 filtered by folder, which is a read-only query with no side effects. It retrieves data without creating, modifying, deleting, executing code, or affecting financial systems. The action is informational and reversible by nature.
From the tool's definition Tool name 'search_test_cases_by_folder' and description 'Search for test cases in a specific folder' indicate a query/retrieval operation with no data modification or execution of external operations.
Attacks that exploit this kind of access
Search for test cases in a specific folder. It is categorised as a Read tool in the Zephyr Scale MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Zephyr Scale MCP Server MCP server in PolicyLayer and add a rule for search_test_cases_by_folder: 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 Zephyr Scale MCP Server. Nothing to install.
search_test_cases_by_folder 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_by_folder 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_by_folder. 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_by_folder is provided by the Zephyr Scale MCP Server MCP server (milo0821/zephyr_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 →