使用 DoWhy GCM 高斯混合密度估计
AI agents invoke gaussian_mixture_density_estimation_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 runs a statistical computation (Gaussian mixture density estimation) using DoWhy's GCM framework. It triggers an external analytical operation whose effects depend on the input data. It does not simply retrieve stored data (Read) nor does it write/modify persistent data — it executes a computation/modeling operation.
From the tool's definition Tool name: 'gaussian_mixture_density_estimation_gcm'; description: '使用 DoWhy GCM 高斯混合密度估计' (Use DoWhy GCM Gaussian mixture density estimation)
Attacks that exploit this kind of access
使用 DoWhy GCM 高斯混合密度估计. 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 gaussian_mixture_density_estimation_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.
gaussian_mixture_density_estimation_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 gaussian_mixture_density_estimation_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 gaussian_mixture_density_estimation_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.
gaussian_mixture_density_estimation_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 →