discrete_additive_noise_model_gcm

WHAT IT DOES

What discrete_additive_noise_model_gcm does on DoWhy MCP v2 0

AI agents use discrete_additive_noise_model_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 discrete_additive_noise_model_gcm needs a policy

The tool creates a model object in memory — a Write operation that instantiates/configures a causal mechanism. It has no destructive, financial, or execution side effects. Severity is low because misuse only results in a misconfigured model object, with no external data modification or system impact.

From the tool's definition 创建离散加性噪声模型 (Create a discrete additive noise model)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

discrete_additive_noise_model_gcm Rate-limited

discrete_additive_noise_model_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": {
    "discrete_additive_noise_model_gcm": {
      "limits": [
        {
          "counter": "discrete_additive_noise_model_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 discrete_additive_noise_model_gcm

What does the discrete_additive_noise_model_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 discrete_additive_noise_model_gcm? +

Register the DoWhy MCP v2 0 MCP server in PolicyLayer and add a rule for discrete_additive_noise_model_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 discrete_additive_noise_model_gcm? +

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

Can I rate-limit discrete_additive_noise_model_gcm? +

Yes. Add a rate_limit block to the discrete_additive_noise_model_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 discrete_additive_noise_model_gcm completely? +

Set action: deny in the PolicyLayer policy for discrete_additive_noise_model_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 discrete_additive_noise_model_gcm? +

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