update_person_channel

Update one contact channel on a person. Person accepts person ID, exact email, or exact display name. Identify the channel with exactly one locator: channelId, or provider plus value. Provide newProvider, newValue, or both. Updating to an existing provider+value on the same person fails with a co...

Server Huly @firfi/huly-mcp
Category Write
Risk class Medium
Parameters 00 required

What update_person_channel does on Huly

AI agents use update_person_channel to create or update resources in Huly — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Huly environment.

Why update_person_channel needs a policy

An AI agent can call update_person_channel faster than any human can review — one bad instruction and it creates or modifies resources in Huly by the hundred, each call as confident as the last.

Questions about update_person_channel

What does the update_person_channel tool do? +

Update one contact channel on a person. Person accepts person ID, exact email, or exact display name. Identify the channel with exactly one locator: channelId, or provider plus value. Provide newProvider, newValue, or both. Updating to an existing provider+value on the same person fails with a conflict. It is categorised as a Write tool in the Huly MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_person_channel? +

Register the Huly MCP server in PolicyLayer and add a rule for update_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 update_person_channel? +

update_person_channel is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_person_channel? +

Yes. Add a rate_limit block to the update_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 update_person_channel completely? +

Set action: deny in the PolicyLayer policy for update_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 update_person_channel? +

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