使用 DoWhy 归因分布变化的根本原因
AI agents call distribution_change_attribution to retrieve information from DoWhy MCP v2 0 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs distribution change attribution analysis using DoWhy, which is a read/query operation that computes statistical attributions from existing data. It does not modify, delete, execute code, or move money. It analyzes causal relationships to identify root causes of distribution changes, which is a read-only analytical operation.
From the tool's definition 归因分布变化的根本原因 (attribute root causes of distribution change) — this is an analytical/read operation performing causal attribution analysis
Attacks that exploit this kind of access
使用 DoWhy 归因分布变化的根本原因. It is categorised as a Read tool in the DoWhy MCP v2 0 MCP Server, which means it retrieves data without modifying state.
Register the DoWhy MCP v2 0 MCP server in PolicyLayer and add a rule for distribution_change_attribution: 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.
distribution_change_attribution is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the distribution_change_attribution 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 distribution_change_attribution. 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.
distribution_change_attribution 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 →