ges_algorithm · DoWhy MCP v2 0 MCP: Risk & Policy

WHAT IT DOES

What ges_algorithm does on DoWhy MCP v2 0

AI agents invoke ges_algorithm 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.

WHY IT NEEDS A POLICY

Why ges_algorithm needs a policy

This tool executes a causal discovery algorithm (Greedy Equivalence Search) on data to infer causal structure. It triggers a computational process that depends on input arguments and produces derived results — fitting the Execute category.

From the tool's definition "运行 GES 算法进行因果发现" (runs GES algorithm for causal discovery)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ges_algorithm Rate-limited

ges_algorithm stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ges_algorithm": {
      "limits": [
        {
          "counter": "ges_algorithm_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 ges_algorithm

What does the ges_algorithm tool do? +

使用 DoWhy 和 causal-learn 运行 GES 算法进行因果发现. 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.

How do I enforce a policy on ges_algorithm? +

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

ges_algorithm is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit ges_algorithm? +

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

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

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