mechanism_change_test_gcm · DoWhy MCP v2 0 MCP

WHAT IT DOES

What mechanism_change_test_gcm does on DoWhy MCP v2 0

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

WHY IT NEEDS A POLICY

Why mechanism_change_test_gcm needs a policy

The tool executes a statistical hypothesis test on causal mechanisms using DoWhy's GCM framework. It does not merely retrieve stored data (it runs a test/computation), nor does it write, delete, or involve finances. The description is brief and in Chinese with no detail on side effects, which lowers confidence slightly.

From the tool's definition '测试机制变化' (test mechanism change) using DoWhy GCM — runs a statistical test/analysis over causal graph mechanisms

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

mechanism_change_test_gcm Rate-limited

mechanism_change_test_gcm 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": {
    "mechanism_change_test_gcm": {
      "limits": [
        {
          "counter": "mechanism_change_test_gcm_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 mechanism_change_test_gcm

What does the mechanism_change_test_gcm tool do? +

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

How do I enforce a policy on mechanism_change_test_gcm? +

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

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

Can I rate-limit mechanism_change_test_gcm? +

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

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

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