config

Manages git configuration values. Supports get, set, list, and unset actions. Operates at local, global, system, or worktree scope.

SERVERBuild SOURCEDave-London/Pare

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dave-london-build/config.md

WHAT IT DOES

What config does on Build

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

RISK

Why config is rated Medium

The tool performs reversible modifications to git configuration (set/unset operations). While 'get' and 'list' are read-only, the presence of 'set' and 'unset' capabilities means it can create or modify configuration state. This is Write rather than Destructive because git config changes are typically reversible (previous values can be restored).

From the tool's definition Tool description states it 'Supports get, set, list, and unset actions' with explicit mention of 'set' and 'unset' operations that modify git configuration values.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs config safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Build, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For config, this is the rule to start with:

config Rate-limited

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": {
    "config": {
      "limits": [
        {
          "counter": "config_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Build, apply this rule, and every config call is checked against it from then on.

FAQ

Questions about config

What does the config tool do? +

Manages git configuration values. Supports get, set, list, and unset actions. Operates at local, global, system, or worktree scope. It is categorised as a Write tool in the Build 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? +

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

What risk level is config? +

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

Can I rate-limit config? +

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

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

config is provided by the Build MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Build, and thousands of servers like it.

This server

All 202 Build tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →