AI agents call testmo_list_automation_runs to retrieve information from Testmo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The naming convention strongly suggests this tool retrieves or enumerates automation runs from the Testmo test management system. No description was provided, which slightly lowers confidence, but the 'list' verb is unambiguous—it fetches data rather than modifies, deletes, or executes operations. The blast radius of misuse is low, as listing data poses minimal risk.
From the tool's definition Tool name 'testmo_list_automation_runs' indicates a retrieval operation ('list' verb). The verb 'list' is characteristic of Read operations that query data without side effects.
Attacks that exploit this kind of access
testmo_list_automation_runs. It is categorised as a Read tool in the Testmo MCP Server, which means it retrieves data without modifying state.
Register the Testmo MCP server in PolicyLayer and add a rule for testmo_list_automation_runs: 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 Testmo. Nothing to install.
testmo_list_automation_runs 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 testmo_list_automation_runs 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 testmo_list_automation_runs. 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.
testmo_list_automation_runs is provided by the Testmo MCP server (strelec00/testmo-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 →