使用 DoWhy GCM 自动估计KL散度
AI agents call auto_estimate_kl_divergence_gcm to retrieve information from DoWhy MCP v2 0 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a statistical estimation (KL divergence) using DoWhy GCM, which is a read/query operation that analyzes data without modifying, executing, or deleting anything. KL divergence is an information-theoretic measure used in causal analysis. No side effects are implied. Confidence is slightly reduced because the description is minimal and in Chinese, offering limited detail about potential side effects.
From the tool's definition '自动估计KL散度' translates to 'automatically estimate KL divergence' — an estimation/read operation that computes a statistical measure
Attacks that exploit this kind of access
使用 DoWhy GCM 自动估计KL散度. It is categorised as a Read tool in the DoWhy MCP v2 0 MCP Server, which means it retrieves data without modifying state.
Register the DoWhy MCP v2 0 MCP server in PolicyLayer and add a rule for auto_estimate_kl_divergence_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.
auto_estimate_kl_divergence_gcm is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the auto_estimate_kl_divergence_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 auto_estimate_kl_divergence_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.
auto_estimate_kl_divergence_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 →