backdoor_estimator · DoWhy MCP v2 0 MCP: Risk & Policy

WHAT IT DOES

What backdoor_estimator does on DoWhy MCP v2 0

AI agents invoke backdoor_estimator 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 backdoor_estimator needs a policy

The tool runs a causal effect estimation algorithm (backdoor adjustment) on data. It executes a statistical/causal computation rather than simply reading stored data or writing new records. It does not delete data (not Destructive) or move money (not Financial). The closest category is Execute, as it performs a domain-specific analytical operation whose results depend on the input arguments and model.

From the tool's definition "估计因果效应" (estimate causal effects) using backdoor adjustment method — triggers a computational causal inference procedure

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

backdoor_estimator Rate-limited

backdoor_estimator 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": {
    "backdoor_estimator": {
      "limits": [
        {
          "counter": "backdoor_estimator_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 backdoor_estimator

What does the backdoor_estimator 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 backdoor_estimator? +

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

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

Can I rate-limit backdoor_estimator? +

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

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

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