config_disable_progress_bars_gcm · DoWhy MCP v2 0 MCP

WHAT IT DOES

What config_disable_progress_bars_gcm does on DoWhy MCP v2 0

AI agents use config_disable_progress_bars_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 config_disable_progress_bars_gcm needs a policy

This tool modifies a configuration/display setting (progress bars) within the DoWhy GCM framework. It writes/updates a configuration value but has no data access, execution, or destructive implications. The blast radius if misused is minimal — it only affects UI/display behavior during analysis runs. Confidence is moderate because the description is brief and in Chinese, providing limited detail.

From the tool's definition '配置进度条显示' (configure progress bar display) — modifies a configuration setting

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

config_disable_progress_bars_gcm Rate-limited

config_disable_progress_bars_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": {
    "config_disable_progress_bars_gcm": {
      "limits": [
        {
          "counter": "config_disable_progress_bars_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 config_disable_progress_bars_gcm

What does the config_disable_progress_bars_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 config_disable_progress_bars_gcm? +

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

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

Can I rate-limit config_disable_progress_bars_gcm? +

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

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

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