Rebases the current branch onto a target branch. Supports abort, continue, skip, and quit for conflict resolution. Returns structured data with success status, branch info, conflicts, and rebased commit count.
AI agents invoke rebase to trigger actions in Python. 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.
A rebase rewrites commit history and modifies branch state. While it can be aborted, the act of rebasing rewrites commits and can cause data loss or force-push scenarios. It triggers an external git operation whose effects depend on arguments, making it Execute-level. The high severity reflects that misuse can corrupt branch history or cause irreversible commit rewrites if followed by a force-push.
From the tool's definition Rebases the current branch onto a target branch. Supports abort, continue, skip, and quit for conflict resolution.
Attacks that exploit this kind of access
Rebases the current branch onto a target branch. Supports abort, continue, skip, and quit for conflict resolution. Returns structured data with success status, branch info, conflicts, and rebased commit count. It is categorised as a Execute tool in the Python MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Python MCP server in PolicyLayer and add a rule for rebase: 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 Python. Nothing to install.
rebase 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 rebase 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 rebase. 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.
rebase is provided by the Python MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
rebase is one line of Python's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →