Start a flood simulation run for a built scenario. The scenario must be in 'built' status. Returns 202 with the new run. The run transitions through: built → queued → computing → processing → complete. After starting, poll get_run_status to track progress. Returns 409 if the scenario is not in th...
Part of the Hydrata - ANUGA Flood Simulation server.
Free to start. No card required.
AI agents invoke start_simulation to trigger processes or run actions in Hydrata - ANUGA Flood Simulation. 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.
start_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": {
"start_simulation": {
"limits": [
{
"counter": "start_simulation_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full Hydrata - ANUGA Flood Simulation policy for all 9 tools.
These attack patterns abuse exactly the kind of access start_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.
Start a flood simulation run for a built scenario. The scenario must be in 'built' status. Returns 202 with the new run. The run transitions through: built → queued → computing → processing → complete. After starting, poll get_run_status to track progress. Returns 409 if the scenario is not in the correct state.. It is categorised as a Execute tool in the Hydrata - ANUGA Flood Simulation MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Hydrata - ANUGA Flood Simulation MCP server in PolicyLayer and add a rule for start_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 Hydrata - ANUGA Flood Simulation. Nothing to install.
start_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 start_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 start_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.
start_simulation is provided by the Hydrata - ANUGA Flood Simulation MCP server (https://hydrata.com/mcp/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 9 Hydrata - ANUGA Flood Simulation 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.