Search tasks by name, tags, or description.
AI agents call search_tasks 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 performs read-only operations—searching and filtering tasks by metadata (name, tags, description). It retrieves information without side effects, altering state, executing code, or committing resources. All sibling tools are similarly read-focused (get_*, find_*, compare_*), reinforcing the pattern that this server provides data access only.
From the tool's definition Tool name 'search_tasks' and description 'Search tasks by name, tags, or description' indicate pure retrieval/query operations with no modification or execution of experiment workflows.
Documented attack patterns abuse exactly the kind of access search_tasks 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 search_tasks:
{
"version": "1",
"default": "deny",
"tools": {
"search_tasks": {}
}
}search_tasks 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.
Search tasks by name, tags, or description. 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 search_tasks: 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.
search_tasks 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 search_tasks 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 search_tasks. 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.
search_tasks 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.