random_common_cause_refuter · DoWhy MCP v2 0 MCP

WHAT IT DOES

What random_common_cause_refuter does on DoWhy MCP v2 0

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

This tool executes a causal inference validation procedure (refutation test) that runs computational analysis to challenge or validate a causal estimate by introducing random common causes. It triggers an external computation/analysis operation rather than simply reading stored data or writing/modifying records.

From the tool's definition '随机共同原因反驳方法' translates to 'random common cause refuter method using DoWhy' — this tool runs a causal refutation/sensitivity analysis procedure that executes a statistical validation algorithm

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

random_common_cause_refuter Rate-limited

random_common_cause_refuter 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": {
    "random_common_cause_refuter": {
      "limits": [
        {
          "counter": "random_common_cause_refuter_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 random_common_cause_refuter

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

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

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

Can I rate-limit random_common_cause_refuter? +

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

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

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