prettier-format
Formats files with Prettier (--write) and returns a structured list of changed files.
This record as markdown: /tools/io-github-dave-london-build/prettier-format.md
What prettier-format does on Build
AI agents use prettier-format 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 prettier-format is rated Medium
This tool modifies files in place (reversibly via version control or undo, but not automatically). File formatting changes are write operations that alter source code. The severity is medium rather than high because formatting is typically a safe, reversible operation compared to data deletion or code execution, though it could affect build outputs or introduce unexpected changes if misconfigured.
From the tool's definition The tool description states it "Formats files with Prettier (--write)" which uses the --write flag to modify files on disk. It "returns a structured list of changed files", confirming file modification occurs.
Attacks that exploit this kind of access
The rule that runs prettier-format 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 prettier-format, this is the rule to start with:
prettier-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 Build, apply this rule, and every prettier-format call is checked against it from then on.
Questions about prettier-format
Formats files with Prettier (--write) and returns a structured list of changed files. 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 prettier-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 Build. Nothing to install.
prettier-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 prettier-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 prettier-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.
prettier-format 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