AI agents invoke fmt to trigger actions in Python. 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.
The tool runs a formatter (likely rustfmt) that can either check or fix Rust code formatting. In 'fix' mode it modifies source files in place, making it a Write/Execute operation. Since it runs an external tool and can overwrite file contents, Execute is the most appropriate category. Severity is medium because misuse could reformat or alter source code, though changes are typically reversible via version control.
From the tool's definition 'fixes Rust formatting' — the tool can modify source files by applying formatting changes
Attacks that exploit this kind of access
Checks or fixes Rust formatting and returns structured output. It is categorised as a Execute tool in the Python MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Python 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 Python. 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 Python MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
fmt is one line of Python's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →