AI agents invoke run-validator to trigger actions in Hyperlane 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.
This tool executes infrastructure operations on blockchain networks. While not directly destructive or financial, running validators has critical blast radius: misconfigured validators could compromise cross-chain message security, enable malicious message relay, or disrupt protocol consensus. The operational impact of an agent incorrectly invoking this tool against production chains is severe.
From the tool's definition Tool name 'run-validator' combined with description 'Runs a validator for a specific chain' indicates execution of external infrastructure operations.
Documented attack patterns abuse exactly the kind of access run-validator gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Hyperlane MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for run-validator:
{
"version": "1",
"default": "deny",
"tools": {
"run-validator": {
"limits": [
{
"counter": "run-validator_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}run-validator 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.
Free to start. No card required.
Runs a validator for a specific chain. It is categorised as a Execute tool in the Hyperlane MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Hyperlane MCP Server MCP server in PolicyLayer and add a rule for run-validator: 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 Hyperlane MCP Server. Nothing to install.
run-validator 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 run-validator 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 run-validator. 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.
run-validator is provided by the Hyperlane MCP Server MCP server (suryansh-23/hyperlane-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Hyperlane MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 Hyperlane MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.