propensity_score_weighting_estimator

WHAT IT DOES

What propensity_score_weighting_estimator does on DoWhy MCP v2 0

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

The tool executes a causal inference estimation algorithm (propensity score weighting) to produce causal effect estimates. It does not merely read stored data, nor does it write/modify persistent data or delete anything. It triggers a computational procedure whose outputs depend on the input arguments (model, data, treatment/outcome specifications), placing it in the Execute category.

From the tool's definition "估计因果效应" (estimates causal effects) using propensity score weighting — runs a statistical estimation procedure that computes causal effect estimates from data

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

propensity_score_weighting_estimator Rate-limited

propensity_score_weighting_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": {
    "propensity_score_weighting_estimator": {
      "limits": [
        {
          "counter": "propensity_score_weighting_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 propensity_score_weighting_estimator

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

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

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

Can I rate-limit propensity_score_weighting_estimator? +

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

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

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