This record as markdown: /tools/io-github-iowarp-adios-mcp/toggle-visibility.md
What toggle_visibility does on CLIO Adios
AI agents use toggle_visibility to create or update resources in CLIO Adios, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CLIO Adios environment.
Why toggle_visibility is rated Medium
Toggling visibility modifies the display/rendering state of a source object in the visualization context, which is a reversible state change (Write). It does not delete data or execute arbitrary code, but it does alter the state of the application.
From the tool's definition Toggle visibility for the active source
Attacks that exploit this kind of access
The rule that runs toggle_visibility safely
PolicyLayer is an MCP gateway: it sits between your AI agents and CLIO Adios, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For toggle_visibility, this is the rule to start with:
toggle_visibility 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 CLIO Adios, apply this rule, and every toggle_visibility call is checked against it from then on.
Questions about toggle_visibility
Toggle visibility for the active source. It is categorised as a Write tool in the CLIO Adios MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the CLIO Adios MCP server in PolicyLayer and add a rule for toggle_visibility: 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 CLIO Adios. Nothing to install.
toggle_visibility 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 toggle_visibility 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 toggle_visibility. 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.
toggle_visibility is provided by the CLIO Adios MCP server (pypi:clio-kit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on CLIO Adios, and thousands of servers like it.
This server
Across the catalogue