This record as markdown: /tools/cloud-easybits-easybits/sandbox-git-push.md
What sandbox_git_push does on EasyBits
AI agents invoke sandbox_git_push to trigger actions in EasyBits. 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 sandbox_git_push is rated High
Pushing to a remote git repo triggers external operations that may overwrite remote state.
From the tool's definition Push a sandbox repo to its remote
Attacks that exploit this kind of access
The rule that runs sandbox_git_push safely
PolicyLayer is an MCP gateway: it sits between your AI agents and EasyBits, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sandbox_git_push, this is the rule to start with:
sandbox_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.
The button opens the PolicyLayer dashboard: create your workspace, connect EasyBits, apply this rule, and every sandbox_git_push call is checked against it from then on.
Questions about sandbox_git_push
Push a sandbox repo to its remote. Pass. It is categorised as a Execute tool in the EasyBits MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the EasyBits MCP server in PolicyLayer and add a rule for sandbox_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 EasyBits. Nothing to install.
sandbox_git_push is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the sandbox_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.
Set action: deny in the PolicyLayer policy for sandbox_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.
sandbox_git_push is provided by the EasyBits MCP server (@easybits.cloud/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on EasyBits, and thousands of servers like it.
Across the catalogue