使用 DoWhy GCM 拟合模型并计算MSE
AI agents invoke fit_and_compute_mse_gcm 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 computational process: fitting a causal graphical model (GCM) to data and computing mean squared error. It runs a potentially expensive operation that transforms input data into model parameters and outputs metrics. It is not purely reading existing data (it modifies internal model state by fitting), and not destructive or financial.
From the tool's definition '拟合模型并计算MSE' (fit model and compute MSE) — triggers a model fitting/training execution and computes a metric
Attacks that exploit this kind of access
使用 DoWhy GCM 拟合模型并计算MSE. 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 fit_and_compute_mse_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.
fit_and_compute_mse_gcm 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 fit_and_compute_mse_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 fit_and_compute_mse_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.
fit_and_compute_mse_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 →