List all active test runs connected to the daemon.
AI agents call list_runs to retrieve information from Mock without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries information about active test runs. The verb 'list' is explicitly a retrieval action that does not create, modify, delete, or execute any operations. It has no side effects and poses minimal risk if misused by an AI agent, as it only exposes read-only visibility into existing test run state.
From the tool's definition Tool name 'list_runs' and description 'List all active test runs connected to the daemon' indicate a data retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access list_runs gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mock, and nothing reaches the server without passing your rules. This is the rule we recommend for list_runs:
{
"version": "1",
"default": "deny",
"tools": {
"list_runs": {}
}
}list_runs is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all active test runs connected to the daemon. It is categorised as a Read tool in the Mock MCP Server, which means it retrieves data without modifying state.
Register the Mock MCP server in PolicyLayer and add a rule for list_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 Mock. Nothing to install.
list_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 list_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 list_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.
list_runs is provided by the Mock MCP server (mcpland/mock-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mock, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 Mock tools catalogued and risk-classified — across an index of 43,000+ MCP servers.