cancel_approval_request
Cancel an active approval Request created by the current Huly user. This is the safe removal-from-workflow operation; hard delete is intentionally not exposed.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/cancel-approval-request.md
What cancel_approval_request does on Huly
AI agents call cancel_approval_request to permanently remove resources in Huly, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why cancel_approval_request is rated Critical
Cancelling an approval request removes it from the active workflow, which is an irreversible state change — the approval request transitions to a terminal cancelled state and cannot be reactivated. While the description frames it as 'safe' and distinguishes it from hard delete, the act of cancelling an in-progress approval is not easily reversible (the workflow state is permanently changed).
From the tool's definition Cancel an active approval Request... safe removal-from-workflow operation; hard delete is intentionally not exposed.
Attacks that exploit this kind of access
The rule that runs cancel_approval_request 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 cancel_approval_request, this is the rule to start with:
cancel_approval_request is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Huly, apply this rule, and every cancel_approval_request call is checked against it from then on.
Questions about cancel_approval_request
Cancel an active approval Request created by the current Huly user. This is the safe removal-from-workflow operation; hard delete is intentionally not exposed. It is categorised as a Destructive tool in the Huly MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Huly MCP server in PolicyLayer and add a rule for cancel_approval_request: 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.
cancel_approval_request is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the cancel_approval_request 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 cancel_approval_request. 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.
cancel_approval_request 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.
Across the catalogue