distance_matching_estimator · DoWhy MCP v2 0 MCP

WHAT IT DOES

What distance_matching_estimator does on DoWhy MCP v2 0

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

This tool runs a causal effect estimation algorithm (distance matching) on data, which constitutes executing an analytical/statistical operation. It does not merely read stored data, nor does it write, delete, or involve finances. The blast radius is medium: misuse could produce misleading causal estimates used in downstream decisions, but it does not alter data or systems directly.

From the tool's definition 估计因果效应 (estimate causal effects) using DoWhy native distance matching method — triggers a computational causal inference estimation process

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

distance_matching_estimator Rate-limited

distance_matching_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": {
    "distance_matching_estimator": {
      "limits": [
        {
          "counter": "distance_matching_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 distance_matching_estimator

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

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

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

Can I rate-limit distance_matching_estimator? +

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

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

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