AI agents call list_manual_test_suites to retrieve information from Testdino without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Even though list_manual_test_suites only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
List the test suite hierarchy to help users find suiteIds for test case creation. Use this to navigate the test suite structure and understand test organization. It is categorised as a Read tool in the Testdino MCP Server, which means it retrieves data without modifying state.
Register the Testdino MCP server in PolicyLayer and add a rule for list_manual_test_suites: 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 Testdino. Nothing to install.
list_manual_test_suites 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 list_manual_test_suites 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 list_manual_test_suites. 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.
list_manual_test_suites is provided by the Testdino MCP server (testdino-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.