AI agents call list_experiments to retrieve information from MLflow MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a query/list operation that retrieves information about experiments. No side effects or modifications occur. The absence of a description reduces confidence slightly, but the naming convention and sibling tools strongly indicate this is a read-only retrieval operation typical of experiment tracking systems.
From the tool's definition Tool name 'list_experiments' indicates retrieval of experiment metadata. Given context of MLflow (ML experiment tracking) and sibling tools ('get_model_details', 'get_system_info', 'list_models') which are all read-only queries, this tool retrieves and lists…
Documented attack patterns abuse exactly the kind of access list_experiments gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MLflow MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_experiments:
{
"version": "1",
"default": "deny",
"tools": {
"list_experiments": {}
}
}list_experiments 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_experiments. It is categorised as a Read tool in the MLflow MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MLflow MCP Server MCP server in PolicyLayer and add a rule for list_experiments: 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 MLflow MCP Server. Nothing to install.
list_experiments 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_experiments 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_experiments. 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_experiments is provided by the MLflow MCP Server MCP server (irahulpandey/mlflowmcpserver). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MLflow MCP Server, 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.
4 MLflow MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.