output
Shows Terraform output values from the current state. Returns structured name/value/type/sensitive data.
This record as markdown: /tools/io-github-dave-london-pare-test/output.md
What output does on Test
AI agents call output to retrieve information from Test without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why output is rated Low
This tool queries and displays existing Terraform state outputs without creating, modifying, deleting, or executing any operations. It is a read-only retrieval operation with minimal risk if misused by an AI agent.
From the tool's definition Tool description states it 'Shows Terraform output values from the current state' and 'Returns structured name/value/type/sensitive data' — purely retrieval with no modification, deletion, or execution of commands.
Attacks that exploit this kind of access
The rule that runs output 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 output, this is the rule to start with:
output 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 Test, apply this rule, and every output call is checked against it from then on.
Questions about output
Shows Terraform output values from the current state. Returns structured name/value/type/sensitive data. It is categorised as a Read tool in the Test MCP Server, which means it retrieves data without modifying state.
Register the Test MCP server in PolicyLayer and add a rule for output: 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.
output 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 output 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 output. 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.
output 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