branch

THE RISK

Critical Risk

Why branch needs a policy

The tool explicitly supports deleting branches, which is an irreversible destructive operation. Since the most severe applicable category applies, and branch deletion cannot be undone (especially on remote repositories), this is classified as Destructive. The blast radius is high as deleting the wrong branch could cause significant data loss in a version control context.

From the tool's definition Lists, creates, renames, or deletes branches

Documented attack patterns abuse exactly the kind of access branch gives an agent:

POLICY

How to control branch

PolicyLayer is an MCP gateway — it sits between your AI agents and Test, and nothing reaches the server without passing your rules. This is the rule we recommend for branch:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "branch"
  ]
}

branch disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Test — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Test tools

Destructive clean Runs dotnet clean to remove build outputs and returns structured results. Destructive remove Runs Destructive reset Resets the current HEAD to a specified state. Supports soft, mixed, hard, merge, and keep Destructive secret-delete Deletes a repository, organization, or environment GitHub Actions secret. Destructive tag Manages git tags. Supports list (default), create, and delete actions. List returns struct Destructive variable-delete Deletes a repository, organization, or environment GitHub Actions variable. Destructive workspace Manages Terraform workspaces: list, select, create, or delete workspaces. Destructive package-clean Cleans Swift package build artifacts and returns structured result.

All 202 Test tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Test → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about branch

What does the branch tool do? +

Lists, creates, renames, or deletes branches. Returns structured branch data. Pass. It is categorised as a Destructive tool in the Test MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on branch? +

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

What risk level is branch? +

branch is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit branch? +

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

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

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

Enforce policy on every Test tool call.

Start from Test, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →