使用 DoWhy 自举法反驳方法
AI agents invoke bootstrap_refuter 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 executes a statistical resampling (bootstrap) procedure to test/refute a causal estimate. It runs computations on existing data without deleting anything or moving money, but it triggers a multi-step analytical execution whose results depend on the arguments supplied. It falls under Execute (runs an analytical/statistical process) rather than Read (pure retrieval) or Write (data modification).
From the tool's definition bootstrap_refuter — applies a bootstrap-based refutation method (自举法反驳方法) which re-samples data and reruns causal estimation procedures
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 bootstrap_refuter: 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.
bootstrap_refuter 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 bootstrap_refuter 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 bootstrap_refuter. 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.
bootstrap_refuter 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 →