preview_action
Dry-run governance preview of a tool call WITHOUT executing it. Validates the args against the tool
This record as markdown: /tools/io-github-heznpc-iconnect/preview-action.md
What preview_action does on Iconnect
AI agents call preview_action to retrieve information from Iconnect without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why preview_action is rated Low
The tool explicitly states it performs a dry-run preview WITHOUT executing the actual action. It only validates arguments, meaning it reads/checks inputs but causes no side effects. This is a read/inspection operation with minimal blast radius.
From the tool's definition Dry-run governance preview of a tool call WITHOUT executing it. Validates the args against the tool
Attacks that exploit this kind of access
The rule that runs preview_action safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Iconnect, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For preview_action, this is the rule to start with:
preview_action 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 Iconnect, apply this rule, and every preview_action call is checked against it from then on.
Questions about preview_action
Dry-run governance preview of a tool call WITHOUT executing it. Validates the args against the tool. It is categorised as a Read tool in the Iconnect MCP Server, which means it retrieves data without modifying state.
Register the Iconnect MCP server in PolicyLayer and add a rule for preview_action: 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 Iconnect. Nothing to install.
preview_action 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 preview_action 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 preview_action. 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.
preview_action is provided by the Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Iconnect, and thousands of servers like it.
This server
Across the catalogue