list_person_channels

List contact channels for a person. Person accepts person ID, exact email address, or exact Huly display name; ambiguous names fail and should be retried with email or person ID.

SERVERHuly SOURCE@firfi/huly-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dearlordylord-huly-mcp/list-person-channels.md

WHAT IT DOES

What list_person_channels does on Huly

AI agents call list_person_channels 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.

RISK

Why list_person_channels is rated Low

This tool queries and retrieves existing contact channel information for a person using their ID, email, or display name as a lookup key. It performs a read-only operation without creating, modifying, deleting, or executing any actions. The blast radius is minimal since it only exposes contact information already associated with a person in the system.

From the tool's definition Tool name 'list_person_channels' and description 'List contact channels for a person' indicate a retrieval operation with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_person_channels 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_person_channels, this is the rule to start with:

list_person_channels Allowed

list_person_channels is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_person_channels": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Huly, apply this rule, and every list_person_channels call is checked against it from then on.

FAQ

Questions about list_person_channels

What does the list_person_channels tool do? +

List contact channels for a person. Person accepts person ID, exact email address, or exact Huly display name; ambiguous names fail and should be retried with email or person ID. It is categorised as a Read tool in the Huly MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_person_channels? +

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

list_person_channels is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_person_channels? +

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

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

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

KEEP EXPLORING

More on Huly, and thousands of servers like it.

This server

All 518 Huly tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →