List runs from an experiment
AI agents call list_runs to retrieve information from MCP DS Toolkit Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns experiment run records without creating, modifying, deleting, or executing any operations. It is a straightforward read operation that retrieves metadata about existing runs. The blast radius of misuse is minimal—an attacker could view run history but cannot modify experiments, delete data, or trigger execution.
From the tool's definition Tool name 'list_runs' and description 'List runs from an experiment' indicate a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
List runs from an experiment. It is categorised as a Read tool in the MCP DS Toolkit Server MCP Server, which means it retrieves data without modifying state.
Register the MCP DS Toolkit Server 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 MCP DS Toolkit Server. 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 MCP DS Toolkit Server MCP server (yasserelhaddar/mcp-ds-toolkit-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 →