update_global_config · Planning Game MCP: Risk & Policy

WHAT IT DOES

What update_global_config does on Planning Game

AI agents use update_global_config to create or update resources in Planning Game — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Planning Game environment.

WHY IT NEEDS A POLICY

Why update_global_config needs a policy

This is a Write operation because it creates or modifies data reversibly. The tool updates existing global configuration but maintains version history and previous content, making changes auditable and potentially reversible.

From the tool's definition Tool name is 'update_global_config' and description states it 'Update[s] an existing global config'. The action modifies configuration data reversibly (versions are retained in history, allowing rollback).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_global_config Rate-limited

update_global_config 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": {
    "update_global_config": {
      "limits": [
        {
          "counter": "update_global_config_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 Planning Game, so you can run agents against it safely.

FAQ

Questions about update_global_config

What does the update_global_config tool do? +

Update an existing global config. For guidelines: auto-increments version and saves previous content in history when content changes. It is categorised as a Write tool in the Planning Game MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_global_config? +

Register the Planning Game MCP server in PolicyLayer and add a rule for update_global_config: 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 Planning Game. Nothing to install.

What risk level is update_global_config? +

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

Can I rate-limit update_global_config? +

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

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

update_global_config is provided by the Planning Game MCP server (planning-game-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.