commit
Creates a commit with the given message. Returns structured data with hash, message, and change statistics. Pass
This record as markdown: /tools/io-github-dave-london-build/commit.md
What commit does on Build
AI agents use commit to create or update resources in Build, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Build environment.
Why commit is rated Medium
Committing is a write operation that modifies version control state. While commits can technically be amended or reset in git, they are committed records intended to persist.
From the tool's definition Tool explicitly "Creates a commit with the given message" — a reversible modification operation that alters the repository state by recording changes.
Attacks that exploit this kind of access
The rule that runs commit safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Build, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For commit, this is the rule to start with:
commit 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 Build, apply this rule, and every commit call is checked against it from then on.
Questions about commit
Creates a commit with the given message. Returns structured data with hash, message, and change statistics. Pass. It is categorised as a Write tool in the Build MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Build MCP server in PolicyLayer and add a rule for commit: 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 Build. Nothing to install.
commit 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 commit 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 commit. 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.
commit is provided by the Build 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 Build, and thousands of servers like it.
This server
Across the catalogue