This record as markdown: /tools/inggerman-mcps/tf-fmt.md
What tf_fmt does on MCP Framework Personal
AI agents invoke tf_fmt to trigger actions in MCP Framework Personal. 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 tf_fmt is rated High
This tool executes a terraform fmt command, which runs an external CLI tool that modifies Terraform configuration files by reformatting them. While terraform fmt is generally considered a safe formatting operation, it does modify files on disk and executes an external process.
From the tool's definition "Ejecuta terraform fmt" — 'ejecuta' means 'executes' in Spanish, indicating this tool runs the Terraform fmt command
Attacks that exploit this kind of access
The rule that runs tf_fmt safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Framework Personal, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For tf_fmt, this is the rule to start with:
tf_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 MCP Framework Personal, apply this rule, and every tf_fmt call is checked against it from then on.
Questions about tf_fmt
Ejecuta terraform fmt. It is categorised as a Execute tool in the MCP Framework Personal MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Framework Personal MCP server in PolicyLayer and add a rule for tf_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 MCP Framework Personal. Nothing to install.
tf_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 tf_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 tf_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.
tf_fmt is provided by the MCP Framework Personal MCP server (inggerman/mcps). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on MCP Framework Personal, and thousands of servers like it.
Across the catalogue