Have Codex generate a training script from experiment config
AI agents invoke codex_generate_training_script to trigger actions in ML Lab MCP. 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.
Generating a training script is more than a write operation because the artifact produced is executable code intended to be run on potentially costly infrastructure (GPU/cloud). Misuse could produce malicious or runaway training scripts that consume significant compute resources or exfiltrate model weights.
From the tool's definition 'generate a training script' and 'from experiment config' — this tool produces executable code/scripts for ML model training, which will be run against GPU backends and cloud providers
Attacks that exploit this kind of access
Have Codex generate a training script from experiment config. It is categorised as a Execute tool in the ML Lab MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the ML Lab MCP server in PolicyLayer and add a rule for codex_generate_training_script: 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 ML Lab MCP. Nothing to install.
codex_generate_training_script 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 codex_generate_training_script 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 codex_generate_training_script. 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.
codex_generate_training_script is provided by the ML Lab MCP server (pushpullcommitpush/ml-mcp). 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 →