add_person_channel
Idempotently add a contact channel to a person. Person accepts person ID, exact email address, or exact Huly display name. Provider labels match list_contact_channel_providers. Returns added=false and the existing channel when the exact provider+value already exists.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/add-person-channel.md
What add_person_channel does on Huly
AI agents use add_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 add_person_channel is rated Medium
This tool creates or modifies contact channel records associated with a person object. While it is idempotent (avoiding true duplication), it is reversible—channels can be removed—so it falls under Write rather than Destructive. Severity is medium because adding a channel could enable unwanted contact routes or information exposure, but blast radius is limited to a single person's contact data.
From the tool's definition Tool explicitly performs an add operation ('add a contact channel to a person') and persists data. The idempotent behavior and return of 'added=false' for duplicates confirms creation/modification semantics rather than retrieval.
Attacks that exploit this kind of access
The rule that runs add_person_channel 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 add_person_channel, this is the rule to start with:
add_person_channel stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 add_person_channel call is checked against it from then on.
Questions about add_person_channel
Idempotently add a contact channel to a person. Person accepts person ID, exact email address, or exact Huly display name. Provider labels match list_contact_channel_providers. Returns added=false and the existing channel when the exact provider+value already exists. 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.
Register the Huly MCP server in PolicyLayer and add a rule for add_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.
add_person_channel is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_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.
Set action: deny in the PolicyLayer policy for add_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.
add_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.
More on Huly, and thousands of servers like it.
This server
Across the catalogue