list_filtered_views
List saved filtered views from @hcengineering/view. Use attachedTo to scope by raw app/resource string such as board:app:Board; omit attachedTo to discover saved views across modules. Reports own/shared visibility from the current account
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/list-filtered-views.md
What list_filtered_views does on Huly
AI agents call list_filtered_views to retrieve information from Huly without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_filtered_views is rated Low
This tool queries and returns filtered views from a project management system (Huly). It retrieves data without side effects, making it a Read operation. Severity is low because the worst outcome is unauthorized access to view definitions that typically reference non-sensitive query parameters, and the blast radius of misuse is limited to information disclosure of view configurations.
From the tool's definition Tool name is 'list_filtered_views' and description explicitly states 'List saved filtered views' — a retrieval operation with no modification. The operation reports visibility metadata but performs no write, delete, or execute actions.
Attacks that exploit this kind of access
The rule that runs list_filtered_views safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Huly, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_filtered_views, this is the rule to start with:
list_filtered_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 Huly, apply this rule, and every list_filtered_views call is checked against it from then on.
Questions about list_filtered_views
List saved filtered views from @hcengineering/view. Use attachedTo to scope by raw app/resource string such as board:app:Board; omit attachedTo to discover saved views across modules. Reports own/shared visibility from the current account. It is categorised as a Read tool in the Huly MCP Server, which means it retrieves data without modifying state.
Register the Huly MCP server in PolicyLayer and add a rule for list_filtered_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 Huly. Nothing to install.
list_filtered_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_filtered_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_filtered_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_filtered_views is provided by the Huly MCP server (@firfi/huly-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Huly, and thousands of servers like it.
This server
Across the catalogue