使用 DoWhy GCM 构建结构因果模型
AI agents use structural_causal_model_builder to create or update resources in DoWhy MCP v2 0 — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DoWhy MCP v2 0 environment.
This tool creates/constructs a structural causal model using DoWhy GCM. Building a model is a Write operation — it creates a new data structure or configuration. It does not execute code, delete data, or involve financial transactions. Severity is medium because a misconfigured causal model could propagate errors into downstream analyses, but the blast radius is limited to analytical outputs rather than system state.
From the tool's definition 构建结构因果模型 — 'build' (构建) indicates creation of a new model artifact
Attacks that exploit this kind of access
使用 DoWhy GCM 构建结构因果模型. It is categorised as a Write tool in the DoWhy MCP v2 0 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the DoWhy MCP v2 0 MCP server in PolicyLayer and add a rule for structural_causal_model_builder: 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.
structural_causal_model_builder is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the structural_causal_model_builder 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 structural_causal_model_builder. 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.
structural_causal_model_builder 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 →