使用 DoWhy 分析反事实公平性
AI agents call counterfactual_fairness 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.
This tool performs causal inference analysis — specifically counterfactual fairness analysis — which is a read/query operation that computes statistical measures over data without modifying or deleting anything. The description indicates analysis ('分析' means 'analyze'), consistent with other sibling tools on this server that are analytical in nature (e.g., anomaly_attribution_analyzer, average_causal_effect_gcm).
From the tool's definition Tool name 'counterfactual_fairness' and description '使用 DoWhy 分析反事实公平性' (Analyze counterfactual fairness using DoWhy)
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 counterfactual_fairness: 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.
counterfactual_fairness 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 counterfactual_fairness 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 counterfactual_fairness. 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.
counterfactual_fairness 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 →