biome-format
Formats files with Biome (format --write) and returns a structured list of changed files.
This record as markdown: /tools/io-github-dave-london-git/biome-format.md
What biome-format does on Git
AI agents use biome-format to create or update resources in Git, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Git environment.
Why biome-format is rated Medium
This tool modifies existing files irreversibly by reformatting their contents. While not destructive in the sense of deletion, it rewrites file content, making it a Write operation.
From the tool's definition Tool description states it 'Formats files with Biome (format --write)' — the '--write' flag indicates the tool modifies files in place rather than just displaying formatting changes.
Attacks that exploit this kind of access
The rule that runs biome-format safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Git, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For biome-format, this is the rule to start with:
biome-format 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 Git, apply this rule, and every biome-format call is checked against it from then on.
Questions about biome-format
Formats files with Biome (format --write) and returns a structured list of changed files. It is categorised as a Write tool in the Git MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Git MCP server in PolicyLayer and add a rule for biome-format: 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 Git. Nothing to install.
biome-format 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 biome-format 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 biome-format. 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.
biome-format is provided by the Git 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 Git, and thousands of servers like it.
This server
Across the catalogue