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-search/output.md
What output does on Search
AI agents call output to retrieve information from Search 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 is a read-only query operation that retrieves and displays Terraform output variables. It has no side effects—it does not create, modify, delete, or execute anything. The data returned may contain sensitive information, but accessing it is a passive read operation. Severity is low because misuse would only expose information already in the Terraform state, not cause infrastructure changes or data loss.
From the tool's definition The tool 'output' performs a retrieval operation: 'Shows Terraform output values from the current state.' It returns structured data (name/value/type/sensitive) without modifying infrastructure or state.
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 Search, 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 Search, 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 Search MCP Server, which means it retrieves data without modifying state.
Register the Search 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 Search. 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 Search 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 Search, and thousands of servers like it.
This server
Across the catalogue