list_approval_requests
List generic Huly approval Request documents from the published @hcengineering/request SDK package. This is read-only discovery: filter by status, raw attachedTo document id, and/or raw attachedToClass class id when you know the target document. Omit filters to inspect recent approval requests ac...
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/list-approval-requests.md
What list_approval_requests does on Huly
AI agents call list_approval_requests 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_approval_requests is rated Low
The tool retrieves and queries approval request data without side effects. The explicit 'read-only discovery' language, combined with filter parameters (status, attachedTo, attachedToClass) for querying existing documents, clearly indicates a retrieval operation. No creation, modification, deletion, or execution of external operations occurs.
From the tool's definition Tool description explicitly states 'This is read-only discovery' and enables filtering/listing of approval request documents with no modification capabilities.
Attacks that exploit this kind of access
The rule that runs list_approval_requests 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_approval_requests, this is the rule to start with:
list_approval_requests 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_approval_requests call is checked against it from then on.
Questions about list_approval_requests
List generic Huly approval Request documents from the published @hcengineering/request SDK package. This is read-only discovery: filter by status, raw attachedTo document id, and/or raw attachedToClass class id when you know the target document. Omit filters to inspect recent approval requests across modules. 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_approval_requests: 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_approval_requests 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_approval_requests 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_approval_requests. 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_approval_requests 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