Stop currently running training job
AI agents invoke stop_training to trigger actions in Ultralytics MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Stopping a training job is an executable action that triggers a state change in an external system (the YOLO training process). While not destructive (training can resume) or financial, it is an active operation that interrupts workflows and could have unintended consequences if triggered inappropriately.
From the tool's definition Tool name 'stop_training' and description 'Stop currently running training job' indicate an external operation that interrupts an active process.
Attacks that exploit this kind of access
Stop currently running training job. It is categorised as a Execute tool in the Ultralytics MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Ultralytics MCP Server MCP server in PolicyLayer and add a rule for stop_training: 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.
stop_training is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the stop_training 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 stop_training. 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.
stop_training 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 →