使用 DoWhy 原生倾向得分分层方法估计因果效应
AI agents invoke propensity_score_stratification_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.
This tool runs a causal inference estimation algorithm (propensity score stratification) that computes statistical estimates from data. It triggers an external computation/analysis operation rather than simply reading stored data or writing/modifying records.
From the tool's definition 使用 DoWhy 原生倾向得分分层方法估计因果效应 (Estimates causal effects using DoWhy native propensity score stratification method)
Attacks that exploit this kind of access
使用 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.
Register the DoWhy MCP v2 0 MCP server in PolicyLayer and add a rule for propensity_score_stratification_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.
propensity_score_stratification_estimator is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the propensity_score_stratification_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.
Set action: deny in the PolicyLayer policy for propensity_score_stratification_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.
propensity_score_stratification_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →