List all training runs with their details and results
AI agents call list_training_history to retrieve information from Ultralytics MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays historical training run information without side effects. It is a pure query operation that reads existing data from the training history. No data is created, modified, deleted, or executed. The worst-case misuse would be unauthorized information disclosure, which has a low blast radius in a typical development environment.
From the tool's definition Tool name 'list_training_history' and description 'List all training runs with their details and results' indicate data retrieval only. No modification, deletion, or code execution is performed.
Attacks that exploit this kind of access
List all training runs with their details and results. It is categorised as a Read tool in the Ultralytics MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Ultralytics MCP Server MCP server in PolicyLayer and add a rule for list_training_history: 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 Ultralytics MCP Server. Nothing to install.
list_training_history 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_training_history 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_training_history. 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_training_history is provided by the Ultralytics MCP Server MCP server (metehanyasar11/ultralytics_mcp_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 →