hyperparameter_search
Run GridSearchCV for a given model type. Returns best params and CV score.
This record as markdown: /tools/agentic-automl-platform/hyperparameter-search.md
What hyperparameter_search does on Agentic Automl Platform
AI agents invoke hyperparameter_search to trigger actions in Agentic Automl Platform. 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 hyperparameter_search is rated High
This tool actively runs a computational process (GridSearchCV) that trains and evaluates many model variants. It does not merely read data or modify stored state reversibly in a simple write sense; it triggers external ML training executions whose cost and output depend on the arguments (model type, parameter grid, dataset).
From the tool's definition 'Run GridSearchCV for a given model type' — executes a cross-validation search process that trains multiple models iteratively
Attacks that exploit this kind of access
The rule that runs hyperparameter_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Agentic Automl Platform, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hyperparameter_search, this is the rule to start with:
hyperparameter_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Agentic Automl Platform, apply this rule, and every hyperparameter_search call is checked against it from then on.
Questions about hyperparameter_search
Run GridSearchCV for a given model type. Returns best params and CV score. It is categorised as a Execute tool in the Agentic Automl Platform MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Agentic Automl Platform MCP server in PolicyLayer and add a rule for hyperparameter_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 Agentic Automl Platform. Nothing to install.
hyperparameter_search 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 hyperparameter_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.
Set action: deny in the PolicyLayer policy for hyperparameter_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.
hyperparameter_search is provided by the Agentic Automl Platform MCP server (anantshri1/agentic-automl-platform). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Agentic Automl Platform, and thousands of servers like it.
Across the catalogue