validate_script
AI agents invoke validate_script to trigger actions in RunWhen Platform 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.
The tool name suggests it validates a script, which likely involves executing or parsing code to check for correctness. Script validation often involves running the script in a sandbox or interpreter. The description is empty, which lowers confidence. Given the context of RunWhen Platform (which deals with automation and runbooks), script validation likely involves some form of execution.
From the tool's definition Tool name contains 'validate_script' — 'script' implies code execution is involved in the validation process
Attacks that exploit this kind of access
validate_script. It is categorised as a Execute tool in the RunWhen Platform MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the RunWhen Platform MCP server in PolicyLayer and add a rule for validate_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 RunWhen Platform MCP. Nothing to install.
validate_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 validate_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 validate_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.
validate_script is provided by the RunWhen Platform MCP server (runwhen-contrib/runwhen-platform-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 →