git_push · Context MCP: Risk & Policy

WHAT IT DOES

What git_push does on Context

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

WHY IT NEEDS A POLICY

Why git_push needs a policy

git push is an external operation that modifies a remote repository's state. While not locally destructive, it can overwrite remote history (especially with force-push), expose code publicly, trigger CI/CD pipelines, and its effects are difficult to reverse on the remote. This qualifies as Execute with high severity due to the blast radius of pushing potentially sensitive or broken code to a shared remote.

From the tool's definition 'Push current branch to remote' — triggers an external git operation that sends commits to a remote repository

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

git_push Rate-limited

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

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Context, so you can run agents against it safely.

FAQ

Questions about git_push

What does the git_push tool do? +

Push current branch to remote. It is categorised as a Execute tool in the Context MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on git_push? +

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

What risk level is git_push? +

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

Can I rate-limit git_push? +

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

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

git_push is provided by the Context MCP server (vibhasdutta/context-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.