intervention_simulator · DoWhy MCP v2 0 MCP: Risk & Policy

WHAT IT DOES

What intervention_simulator does on DoWhy MCP v2 0

AI agents invoke intervention_simulator to trigger actions in DoWhy MCP v2 0. 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.

WHY IT NEEDS A POLICY

Why intervention_simulator needs a policy

The tool executes causal intervention simulations, triggering computational processes whose results depend on the specified interventions and model arguments. It does not merely read static data, nor does it irreversibly delete or modify persistent data. It falls under Execute as it runs a simulation engine with dynamic, argument-dependent outputs.

From the tool's definition '模拟多种干预效果' (simulate multiple intervention effects) — the tool runs simulations/executes causal interventions using DoWhy

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

intervention_simulator Rate-limited

intervention_simulator 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "intervention_simulator": {
      "limits": [
        {
          "counter": "intervention_simulator_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches DoWhy MCP v2 0, so you can run agents against it safely.

FAQ

Questions about intervention_simulator

What does the intervention_simulator tool do? +

使用 DoWhy 模拟多种干预效果. It is categorised as a Execute tool in the DoWhy MCP v2 0 MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on intervention_simulator? +

Register the DoWhy MCP v2 0 MCP server in PolicyLayer and add a rule for intervention_simulator: 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 DoWhy MCP v2 0. Nothing to install.

What risk level is intervention_simulator? +

intervention_simulator is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit intervention_simulator? +

Yes. Add a rate_limit block to the intervention_simulator 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.

How do I block intervention_simulator completely? +

Set action: deny in the PolicyLayer policy for intervention_simulator. 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.

What MCP server provides intervention_simulator? +

intervention_simulator is provided by the DoWhy MCP v2 0 MCP server (lesong36/dowhy_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.