设置可选模型 API provider 和 model。
AI agents use set_model_provider 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.
This tool creates or modifies configuration data (API provider and model settings) without deleting or executing arbitrary code. It's a reversible write operation that changes system settings. Severity is medium because misconfiguration could affect tool behavior downstream, but the direct blast radius is limited to configuration state rather than data deletion or financial impact.
From the tool's definition Tool description indicates 'set' operation (设置 means 'set/configure' in Chinese) for model API provider and model configuration. This modifies application configuration state.
Attacks that exploit this kind of access
设置可选模型 API provider 和 model。. 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.
Register the GitBranch MCP server in PolicyLayer and add a rule for set_model_provider: 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.
set_model_provider 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 set_model_provider 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 set_model_provider. 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.
set_model_provider 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →