AI agents call search_logged_models 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 name indicates searching/querying logged models, which is a retrieval operation. While the description is empty (lowering confidence slightly), the context of MLflow's tracking and querying functionality, combined with sibling tools that clearly perform read operations, strongly suggests this searches model metadata without modification or deletion.
From the tool's definition Tool name 'search_logged_models' with context from sibling tools (get_artifact_content, get_best_run, get_experiment_by_name) all follow read-only query patterns.
Documented attack patterns abuse exactly the kind of access search_logged_models 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 search_logged_models:
{
"version": "1",
"default": "deny",
"tools": {
"search_logged_models": {}
}
}search_logged_models 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_logged_models. 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 search_logged_models: 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.
search_logged_models 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_logged_models 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_logged_models. 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_logged_models is provided by the MLflow MCP Server MCP server (kkruglik/mlflow-mcp). 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.
40 MLflow MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.