remove_person_channel

Remove one contact channel from a person. Person accepts person ID, exact email, or exact display name. Identify the channel with exactly one locator: channelId, or provider plus value. Returns removed=false when the locator is absent for that person.

Server Huly @firfi/huly-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What remove_person_channel does on Huly

AI agents call remove_person_channel 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 remove_person_channel needs a policy

An AI agent that decides to call remove_person_channel doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Huly is gone — there is no undo for destructive operations.

Questions about remove_person_channel

What does the remove_person_channel tool do? +

Remove one contact channel from a person. Person accepts person ID, exact email, or exact display name. Identify the channel with exactly one locator: channelId, or provider plus value. Returns removed=false when the locator is absent for that person. 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.

How do I enforce a policy on remove_person_channel? +

Register the Huly MCP server in PolicyLayer and add a rule for remove_person_channel: 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.

What risk level is remove_person_channel? +

remove_person_channel is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit remove_person_channel? +

Yes. Add a rate_limit block to the remove_person_channel 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.

How do I block remove_person_channel completely? +

Set action: deny in the PolicyLayer policy for remove_person_channel. 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.

What MCP server provides remove_person_channel? +

remove_person_channel 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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.