get_filtered_view
Get one saved filtered view by FilteredView _id or exact name. Pass attachedTo, such as board:app:Board, when an exact name may exist in more than one module. Read-only; no saved-view writes are performed.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/get-filtered-view.md
What get_filtered_view does on Huly
AI agents call get_filtered_view 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 get_filtered_view is rated Low
This tool retrieves saved filtered view data by ID or name. It performs no modifications, deletions, or external operations. The explicit 'Read-only' designation confirms it belongs in the Read category with low severity—typical data retrieval poses minimal risk even if an AI agent calls it with arbitrary parameters.
From the tool's definition Tool description explicitly states 'Get one saved filtered view' and 'Read-only; no saved-view writes are performed.' The tool retrieves/queries data without side effects.
Attacks that exploit this kind of access
The rule that runs get_filtered_view 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 get_filtered_view, this is the rule to start with:
get_filtered_view 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 get_filtered_view call is checked against it from then on.
Questions about get_filtered_view
Get one saved filtered view by FilteredView _id or exact name. Pass attachedTo, such as board:app:Board, when an exact name may exist in more than one module. Read-only; no saved-view writes are performed. 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 get_filtered_view: 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.
get_filtered_view 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 get_filtered_view 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 get_filtered_view. 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.
get_filtered_view 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