create_discrete_density_estimator_gcm

WHAT IT DOES

What create_discrete_density_estimator_gcm does on DoWhy MCP v2 0

AI agents use create_discrete_density_estimator_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.

WHY IT NEEDS A POLICY

Why create_discrete_density_estimator_gcm needs a policy

The tool creates a discrete density estimator, which is a Write operation (constructing a new in-memory object or configuration). It does not appear to execute queries, delete data, or move money. Severity is low because creating an estimator is a preparatory modeling step with minimal blast radius — it does not directly alter datasets or trigger external side effects.

From the tool's definition '创建' (create) — the tool name explicitly starts with 'create', indicating it instantiates/constructs a discrete density estimator object using DoWhy GCM

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_discrete_density_estimator_gcm Rate-limited

create_discrete_density_estimator_gcm stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_discrete_density_estimator_gcm": {
      "limits": [
        {
          "counter": "create_discrete_density_estimator_gcm_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches DoWhy MCP v2 0, so you can run agents against it safely.

FAQ

Questions about create_discrete_density_estimator_gcm

What does the create_discrete_density_estimator_gcm tool do? +

使用 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.

How do I enforce a policy on create_discrete_density_estimator_gcm? +

Register the DoWhy MCP v2 0 MCP server in PolicyLayer and add a rule for create_discrete_density_estimator_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.

What risk level is create_discrete_density_estimator_gcm? +

create_discrete_density_estimator_gcm is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_discrete_density_estimator_gcm? +

Yes. Add a rate_limit block to the create_discrete_density_estimator_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.

How do I block create_discrete_density_estimator_gcm completely? +

Set action: deny in the PolicyLayer policy for create_discrete_density_estimator_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.

What MCP server provides create_discrete_density_estimator_gcm? +

create_discrete_density_estimator_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.