state-list
Lists all resources tracked in the Terraform state. Returns resource addresses.
This record as markdown: /tools/io-github-dave-london-go/state-list.md
What state-list does on Go
AI agents call state-list 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 state-list is rated Low
The tool performs a read-only query of Terraform state to enumerate resources. It retrieves and displays information without side effects. While the state file may contain sensitive data (credentials, secrets), the misuse risk is limited to information disclosure rather than infrastructure modification or destruction.
From the tool's definition Tool name 'state-list' and description 'Lists all resources tracked in the Terraform state. Returns resource addresses.' indicate a retrieval operation with no modification or deletion of state.
Attacks that exploit this kind of access
The rule that runs state-list 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 state-list, this is the rule to start with:
state-list 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 state-list call is checked against it from then on.
Questions about state-list
Lists all resources tracked in the Terraform state. Returns resource addresses. 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 state-list: 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.
state-list 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 state-list 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 state-list. 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.
state-list 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