Get status and results of an ongoing or completed grid search
AI agents call get_grid_search_status 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 information about an existing grid search operation. The verb 'Get' and the focus on obtaining 'status and results' are characteristic of Read operations. There is no indication the tool modifies data, executes code, deletes anything, or involves financial transactions. The blast radius of misuse is minimal since it only queries state information.
From the tool's definition Tool name 'get_grid_search_status' and description 'Get status and results of an ongoing or completed grid search' indicate retrieval of status and results data without modification or execution.
Attacks that exploit this kind of access
Get status and results of an ongoing or completed grid search. 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 get_grid_search_status: 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.
get_grid_search_status 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 get_grid_search_status 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 get_grid_search_status. 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.
get_grid_search_status 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 →