list_views
List all named views in the document plus the currently active view.
This record as markdown: /tools/hybridlabor-api-aos/list-views.md
What list_views does on Aos
AI agents call list_views to retrieve information from Aos without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_views is rated Low
This tool queries and returns information about views in a Rhino document without creating, modifying, deleting, or executing any operations. It has no side effects and falls squarely into the Read category with low severity since it only exposes metadata about the document state.
From the tool's definition Tool name is 'list_views' and description states 'List all named views in the document plus the currently active view.' The verb 'list' and action of retrieving/querying view metadata with no modifications indicate a read-only operation.
Attacks that exploit this kind of access
The rule that runs list_views safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_views, this is the rule to start with:
list_views 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 Aos, apply this rule, and every list_views call is checked against it from then on.
Questions about list_views
List all named views in the document plus the currently active view. It is categorised as a Read tool in the Aos MCP Server, which means it retrieves data without modifying state.
Register the Aos MCP server in PolicyLayer and add a rule for list_views: 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 Aos. Nothing to install.
list_views 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 list_views 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 list_views. 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.
list_views is provided by the Aos MCP server (@hybridlabor-api/aos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aos, and thousands of servers like it.
This server
Across the catalogue