Submit a server-side RF simulation job and wait for the result. Requires RFTOOLS_API_KEY environment variable. Simulations typically complete in 15\u2013120 seconds; queue wait may add more time. Use list_simulation_tools to see available jobTypes and required params.
Part of the Rftools server.
Free to start. No card required.
AI agents invoke run_simulation to trigger processes or run actions in Rftools. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
run_simulation can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
{
"version": "1",
"default": "deny",
"tools": {
"run_simulation": {
"limits": [
{
"counter": "run_simulation_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full Rftools policy for all 5 tools.
These attack patterns abuse exactly the kind of access run_simulation gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Submit a server-side RF simulation job and wait for the result. Requires RFTOOLS_API_KEY environment variable. Simulations typically complete in 15\u2013120 seconds; queue wait may add more time. Use list_simulation_tools to see available jobTypes and required params.. It is categorised as a Execute tool in the Rftools MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Rftools MCP server in PolicyLayer and add a rule for run_simulation: 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 Rftools. Nothing to install.
run_simulation 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_simulation 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_simulation. 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_simulation is provided by the Rftools MCP server (rftools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 5 Rftools tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.