stop_grid_search · Ultralytics MCP Server MCP: Risk & Policy

WHAT IT DOES

What stop_grid_search does on Ultralytics MCP Server

AI agents invoke stop_grid_search 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.

WHY IT NEEDS A POLICY

Why stop_grid_search needs a policy

Stopping a grid search is an Execute action because it triggers a control operation (interruption/termination) on an external computational process. While not destructive (the grid search can be restarted), it disrupts an ongoing operation. The blast radius is medium because halting a training job wastes compute resources and loses intermediate progress, but can be restarted without data loss.

From the tool's definition Tool description states 'Stop a running grid search' — this terminates an active external process/operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stop_grid_search Rate-limited

stop_grid_search stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "stop_grid_search": {
      "limits": [
        {
          "counter": "stop_grid_search_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Ultralytics MCP Server, so you can run agents against it safely.

FAQ

Questions about stop_grid_search

What does the stop_grid_search tool do? +

Stop a running grid search and return best results so far. 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.

How do I enforce a policy on stop_grid_search? +

Register the Ultralytics MCP Server MCP server in PolicyLayer and add a rule for stop_grid_search: 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.

What risk level is stop_grid_search? +

stop_grid_search is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit stop_grid_search? +

Yes. Add a rate_limit block to the stop_grid_search 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.

How do I block stop_grid_search completely? +

Set action: deny in the PolicyLayer policy for stop_grid_search. 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.

What MCP server provides stop_grid_search? +

stop_grid_search 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.