biome-check
Runs Biome check (lint + format) and returns structured diagnostics (file, line, rule, severity, message).
This record as markdown: /tools/io-github-dave-london-go/biome-check.md
What biome-check does on Go
AI agents call biome-check to retrieve information from Go without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why biome-check is rated Low
Biome check is a static analysis and linting tool that inspects code for style, format, and logical issues. It reads files and returns diagnostic information without creating, modifying, deleting, executing commands, or triggering external operations. The output is purely informational diagnostics used to report code quality issues.
From the tool's definition Runs Biome check (lint + format) and returns structured diagnostics (file, line, rule, severity, message)—read-only analysis with no data modification or side effects.
Attacks that exploit this kind of access
The rule that runs biome-check safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Go, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For biome-check, this is the rule to start with:
biome-check is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Go, apply this rule, and every biome-check call is checked against it from then on.
Questions about biome-check
Runs Biome check (lint + format) and returns structured diagnostics (file, line, rule, severity, message). It is categorised as a Read tool in the Go MCP Server, which means it retrieves data without modifying state.
Register the Go 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 Go. Nothing to install.
biome-check is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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 Go 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 Go, and thousands of servers like it.
This server
Across the catalogue