checkout
Switches branches or restores files. Returns structured data with ref, previous ref, whether a new branch was created, and detached HEAD status. Pass
This record as markdown: /tools/io-github-dave-london-pare-test/checkout.md
What checkout does on Test
AI agents use checkout to create or update resources in Test, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Test environment.
Why checkout is rated Medium
Git checkout can both switch between existing branches and restore/overwrite files in the working directory. While not destructive in the sense of permanent deletion, it modifies the repository state reversibly—users can switch back or restore from the index. This is a Write operation rather than Execute because the effects are primarily about changing version control state rather than running arbitrary code.
From the tool's definition Tool 'checkout' performs git checkout operations that modify the current working branch state: 'Switches branches or restores files' and tracks 'whether a new branch was created' and 'detached HEAD status'.
Attacks that exploit this kind of access
The rule that runs checkout safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Test, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For checkout, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Test, apply this rule, and every checkout call is checked against it from then on.
Questions about checkout
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 Test MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Test 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 Test. 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 Test MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Test, and thousands of servers like it.
This server
Across the catalogue