Switches branches or restores files. Returns structured data with ref, previous ref, whether a new branch was created, and detached HEAD status. Pass
AI agents use checkout to create or update resources in Make — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Make environment.
The checkout operation creates, modifies, or changes repository state by switching branches or restoring files. This is reversible (can checkout back to previous state or switch branches again), so it falls under Write rather than Destructive. However, restoring files could overwrite local changes, warranting medium severity due to potential unintended data loss if misused by an AI agent without proper safeguards.
From the tool's definition Tool description states it 'Switches branches or restores files' and returns metadata including 'whether a new branch was created' and 'detached HEAD status'.
Documented attack patterns abuse exactly the kind of access checkout gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Make, and nothing reaches the server without passing your rules. This is the rule we recommend for checkout:
{
"version": "1",
"default": "deny",
"tools": {
"checkout": {
"limits": [
{
"counter": "checkout_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}checkout stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Switches branches or restores files. Returns structured data with ref, previous ref, whether a new branch was created, and detached HEAD status. Pass. It is categorised as a Write tool in the Make MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Make MCP server in PolicyLayer and add a rule for checkout: 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 Make. Nothing to install.
checkout is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the checkout 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 checkout. 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.
checkout is provided by the Make MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Make, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
202 Make tools catalogued and risk-classified — across an index of 43,000+ MCP servers.