isolation_forest_scorer_gcm · DoWhy MCP v2 0 MCP

WHAT IT DOES

What isolation_forest_scorer_gcm does on DoWhy MCP v2 0

AI agents invoke isolation_forest_scorer_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 isolation_forest_scorer_gcm needs a policy

The tool runs a machine learning algorithm (Isolation Forest) to compute anomaly scores, which constitutes executing an analytical/computational operation. It reads data but the primary action is running a model, placing it in Execute rather than Read. No data is modified, deleted, or financial transactions are made, so Execute is the most appropriate category.

From the tool's definition '使用 DoWhy GCM 孤立森林异常评分器' — applies an Isolation Forest anomaly scoring algorithm via the DoWhy GCM module, triggering a computational model execution

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

isolation_forest_scorer_gcm Rate-limited

isolation_forest_scorer_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": {
    "isolation_forest_scorer_gcm": {
      "limits": [
        {
          "counter": "isolation_forest_scorer_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 isolation_forest_scorer_gcm

What does the isolation_forest_scorer_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 isolation_forest_scorer_gcm? +

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

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

Can I rate-limit isolation_forest_scorer_gcm? +

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

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

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