fmt
Checks or fixes Rust formatting and returns structured output.
This record as markdown: /tools/io-github-dave-london-pare-test/fmt.md
What fmt does on Test
AI agents invoke fmt to trigger actions in Test. 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.
Why fmt is rated High
The tool runs a formatting operation (likely `rustfmt`) that can either check formatting or fix it by rewriting source files. When in fix mode, it modifies files on disk, making it at least a Write operation. Since it also executes an external process/command (rustfmt), Execute is the most appropriate category. It spans Write and Execute; Execute wins per severity rules.
From the tool's definition 'Checks or fixes Rust formatting' — the tool can actively modify source files when fixing formatting
Attacks that exploit this kind of access
The rule that runs fmt safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Test, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For fmt, this is the rule to start with:
fmt 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Test, apply this rule, and every fmt call is checked against it from then on.
Questions about fmt
Checks or fixes Rust formatting and returns structured output. It is categorised as a Execute tool in the Test MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Test MCP server in PolicyLayer and add a rule for fmt: 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 Test. Nothing to install.
fmt 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 fmt 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 fmt. 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.
fmt is provided by the Test 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 Test, and thousands of servers like it.
This server
Across the catalogue