repo_sync

THE RISK

Critical Risk

Why repo_sync needs a policy

The 'cleanup merged branches' portion of this tool's action is irreversible — deleting local (and potentially remote) branches that have been merged. Branch deletion cannot be undone without additional git recovery steps, and remote branch deletion is permanent. This qualifies as Destructive. The sync portion alone would be Write/Execute, but the most severe applicable category wins.

From the tool's definition Sync with remote and cleanup merged branches

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

POLICY

How to control repo_sync

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

policy.json

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

repo_sync 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 MCP DevTools Server — 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 MCP DevTools Server tools

Execute python_venv Manage Python virtual environments (create, delete, info, list packages) Execute commitlint Run commitlint to validate commit messages Execute eslint Run ESLint on JavaScript/TypeScript files Execute go_benchmark Run Go benchmarks to measure code performance Execute go_build Build Go packages with cross-compilation and custom build flags support Execute lint_all Run all available linters based on project type Execute lint_files Run custom linting rules on project files Execute make_build Run make build command to build the project

All 79 MCP DevTools Server 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 MCP DevTools Server → 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 repo_sync

What does the repo_sync tool do? +

Sync with remote and cleanup merged branches. It is categorised as a Destructive tool in the MCP DevTools Server 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 repo_sync? +

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

What risk level is repo_sync? +

repo_sync 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 repo_sync? +

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

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

repo_sync is provided by the MCP DevTools Server MCP server (rshade/mcp-devtools-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP DevTools Server tool call.

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

CHECK YOUR STACK →