set_git_config

Enable/configure optional per-project git integration so finished tickets can be committed (and optionally pushed) to the project

SERVERFeatureBoard SOURCEhttps://github.com/valentil/featureboard-mcp/releases/download/v0.7/featureboard.plugin

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ai-featureboard-featureboard/set-git-config.md

WHAT IT DOES

What set_git_config does on FeatureBoard

AI agents invoke set_git_config to trigger actions in FeatureBoard. 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.

RISK

Why set_git_config is rated High

This tool configures git integration that triggers external git operations (commits and pushes) on a project repository. Committing and pushing code to a repository is an Execute-level operation with potentially high blast radius — a misconfigured push could modify or overwrite branches in a remote repository.

From the tool's definition 'Enable/configure optional per-project git integration so finished tickets can be committed (and optionally pushed) to the project'

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs set_git_config safely

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

set_git_config Rate-limited

set_git_config 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": {
    "set_git_config": {
      "limits": [
        {
          "counter": "set_git_config_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about set_git_config

What does the set_git_config tool do? +

Enable/configure optional per-project git integration so finished tickets can be committed (and optionally pushed) to the project. It is categorised as a Execute tool in the FeatureBoard MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on set_git_config? +

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

What risk level is set_git_config? +

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

Can I rate-limit set_git_config? +

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

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

set_git_config is provided by the FeatureBoard MCP server (https://github.com/valentil/featureboard-mcp/releases/download/v0.7/featureboard.plugin). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on FeatureBoard, and thousands of servers like it.

This server

All 215 FeatureBoard tools → High-risk tools on this server →

Across the catalogue

set_breakpoint on Frida Game Hacking MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →