set_model_api_key · GitBranch MCP: Risk & Policy

WHAT IT DOES

What set_model_api_key does on GitBranchMCP

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

WHY IT NEEDS A POLICY

Why set_model_api_key needs a policy

This tool writes sensitive API keys to persistent storage. While not destructive (the action is reversible by overwriting with a new key), it is a Write operation that modifies application state/configuration. Severity is high because misuse could result in credential compromise, unauthorized API access, or service disruption if malicious keys are injected.

From the tool's definition Tool name 'set_model_api_key' and description '保存可选模型 API Key' (Save optional model API Key) indicate the tool creates or modifies stored credentials/configuration data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_model_api_key Rate-limited

set_model_api_key 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": {
    "set_model_api_key": {
      "limits": [
        {
          "counter": "set_model_api_key_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 GitBranchMCP, so you can run agents against it safely.

FAQ

Questions about set_model_api_key

What does the set_model_api_key tool do? +

保存可选模型 API Key。. It is categorised as a Write tool in the GitBranchMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_model_api_key? +

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

What risk level is set_model_api_key? +

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

Can I rate-limit set_model_api_key? +

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

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

set_model_api_key is provided by the GitBranch MCP server (lianggaoyuan/gitbranchmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.