Find experiments in a specific project by name pattern.
AI agents call find_experiment_in_project to retrieve information from Clearml without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries experiment data based on a pattern match within a project. It is a read-only operation that returns matching results without creating, modifying, deleting, or executing any operations. The pattern-based search is analogous to a filtered list or search query, which is a classic Read category action.
From the tool's definition Tool name includes 'find' and description states 'Find experiments in a specific project by name pattern' - a search/query operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access find_experiment_in_project gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Clearml, and nothing reaches the server without passing your rules. This is the rule we recommend for find_experiment_in_project:
{
"version": "1",
"default": "deny",
"tools": {
"find_experiment_in_project": {}
}
} find_experiment_in_project 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.
Find experiments in a specific project by name pattern. It is categorised as a Read tool in the Clearml MCP Server, which means it retrieves data without modifying state.
Register the Clearml MCP server in PolicyLayer and add a rule for find_experiment_in_project: 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 Clearml. Nothing to install.
find_experiment_in_project 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 find_experiment_in_project 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 find_experiment_in_project. 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.
find_experiment_in_project is provided by the Clearml MCP server (prassanna-ravishankar/clearml-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Clearml, 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.
14 Clearml tools catalogued and risk-classified — across an index of 43,000+ MCP servers.