This record as markdown: /tools/inggerman-mcps/tf-import.md
What tf_import does on MCP Framework Personal
AI agents use tf_import to create or update resources in MCP Framework Personal, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Framework Personal environment.
Why tf_import is rated Medium
This tool writes to Terraform state, creating or modifying the mapping between infrastructure resources and Terraform's internal tracking. While not destructive (state can be updated), it is a Write operation with high severity due to the potential to misdirect infrastructure management, cause drift detection issues, or inadvertently claim ownership of unmanaged resources.
From the tool's definition Tool description states 'Importa un recurso al state' (Imports a resource to state), which indicates modifying Terraform state—a critical infrastructure configuration store.
Attacks that exploit this kind of access
The rule that runs tf_import 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_import, this is the rule to start with:
tf_import stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_import call is checked against it from then on.
Questions about tf_import
Importa un recurso al state. It is categorised as a Write tool in the MCP Framework Personal MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Framework Personal MCP server in PolicyLayer and add a rule for tf_import: 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_import is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the tf_import 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_import. 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_import 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.
This server
Across the catalogue