Manages git configuration values. Supports get, set, list, and unset actions. Operates at local, global, system, or worktree scope.
AI agents use config to create or update resources in Make — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Make environment.
The tool modifies git configuration (set/unset) rather than just reading it (get/list), making it a Write operation. While configuration changes are generally reversible, they can affect git behavior system-wide depending on scope (local, global, system, worktree).
From the tool's definition Tool description states 'Supports get, set, list, and unset actions.' The 'set' and 'unset' actions modify git configuration values, which are changes to system/user settings that can be reversed.
Documented attack patterns abuse exactly the kind of access config gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Make, and nothing reaches the server without passing your rules. This is the rule we recommend for config:
{
"version": "1",
"default": "deny",
"tools": {
"config": {
"limits": [
{
"counter": "config_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
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 Make MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Make 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 Make. Nothing to install.
config is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
config is provided by the Make MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Make, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
202 Make tools catalogued and risk-classified — across an index of 43,000+ MCP servers.