使用 DoWhy 分析路径特定效应
AI agents call path_specific_effects 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 causal inference analysis (reading and computing statistical estimates from a causal model). There is no indication it modifies data, executes external commands, deletes anything, or moves money. The description is minimal (Chinese: 'analyze path-specific effects using DoWhy'), so confidence is moderate.
From the tool's definition 路径特定效应 (path-specific effects) — the tool analyzes causal path-specific effects using DoWhy, which is a read/query operation over a causal model
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 path_specific_effects: 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.
path_specific_effects 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 path_specific_effects 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 path_specific_effects. 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.
path_specific_effects 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 →