使用 DoWhy GCM Scipy分布建模
AI agents use scipy_distribution_gcm 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.
The tool appears to model/assign a Scipy distribution as a causal mechanism in a GCM (Generalized Causal Model). Based on sibling tools like 'assign_causal_mechanisms', this likely writes/configures a distribution model into the causal graph rather than reading or executing external operations. Confidence is moderate because the description is minimal and in Chinese, offering limited detail about side effects.
From the tool's definition 使用 DoWhy GCM Scipy分布建模 (Using DoWhy GCM Scipy distribution modeling)
Attacks that exploit this kind of access
使用 DoWhy GCM Scipy分布建模. 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 scipy_distribution_gcm: 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.
scipy_distribution_gcm 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 scipy_distribution_gcm 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 scipy_distribution_gcm. 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.
scipy_distribution_gcm 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 →