Runs Biome check (lint + format) and returns structured diagnostics (file, line, rule, severity, message).
AI agents invoke biome-check to trigger actions in Make. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool runs an external process (Biome) to lint and format code. While primarily read-like in intent (checking/reporting), it executes an external tool that could apply formatting changes to files and has side effects beyond simple data retrieval. Classified as Execute due to running an external process; severity is medium as it could modify source files during format operations.
From the tool's definition 'Runs Biome check' — executes an external linting and formatting tool against code files
Documented attack patterns abuse exactly the kind of access biome-check 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 biome-check:
{
"version": "1",
"default": "deny",
"tools": {
"biome-check": {
"limits": [
{
"counter": "biome-check_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}biome-check stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Runs Biome check (lint + format) and returns structured diagnostics (file, line, rule, severity, message). It is categorised as a Execute tool in the Make MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Make MCP server in PolicyLayer and add a rule for biome-check: 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.
biome-check is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the biome-check 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-check. 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-check 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.