assign_causal_mechanisms · DoWhy MCP v2 0 MCP: Risk & Policy

WHAT IT DOES

What assign_causal_mechanisms does on DoWhy MCP v2 0

AI agents use assign_causal_mechanisms to create or update resources in DoWhy MCP v2 0 — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DoWhy MCP v2 0 environment.

WHY IT NEEDS A POLICY

Why assign_causal_mechanisms needs a policy

The tool assigns (writes) causal mechanisms to a causal graph model, modifying its configuration. This is a reversible write operation — the model can be reconfigured — rather than destructive or executing external code. Severity is medium because misconfigured causal mechanisms could lead to incorrect downstream analyses, but the blast radius is limited to the model state.

From the tool's definition '自动分配因果机制' (automatically assign causal mechanisms) — assigns/sets causal mechanisms to nodes in a causal model graph

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

assign_causal_mechanisms Rate-limited

assign_causal_mechanisms stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "assign_causal_mechanisms": {
      "limits": [
        {
          "counter": "assign_causal_mechanisms_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 assign_causal_mechanisms

What does the assign_causal_mechanisms tool do? +

使用 DoWhy GCM 自动分配因果机制. It is categorised as a Write tool in the DoWhy MCP v2 0 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on assign_causal_mechanisms? +

Register the DoWhy MCP v2 0 MCP server in PolicyLayer and add a rule for assign_causal_mechanisms: 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 assign_causal_mechanisms? +

assign_causal_mechanisms is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit assign_causal_mechanisms? +

Yes. Add a rate_limit block to the assign_causal_mechanisms 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 assign_causal_mechanisms completely? +

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

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