list_persons

List all persons in the Huly workspace. Returns persons sorted by modification date (newest first). Supports searching by name substring (nameSearch) and email substring (emailSearch).

SERVERHuly SOURCEdugynoo/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/dugynoo-huly-mcp/list-persons.md

WHAT IT DOES

What list_persons does on Huly

AI agents call list_persons 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_persons is rated Low

This is a read-only operation that retrieves and queries person data from the Huly workspace with optional filtering. It has no side effects, cannot modify data, and returns information. The blast radius is minimal—an agent could potentially discover user information but cannot act on it or change it with this tool alone.

From the tool's definition Tool name 'list_persons' and description explicitly states it 'List all persons' and 'Returns persons sorted by modification date'. Supports searching by name and email substrings. No modification, deletion, or execution described.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

list_persons Allowed

list_persons 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_persons": {}
  }
}

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_persons call is checked against it from then on.

FAQ

Questions about list_persons

What does the list_persons tool do? +

List all persons in the Huly workspace. Returns persons sorted by modification date (newest first). Supports searching by name substring (nameSearch) and email substring (emailSearch). 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_persons? +

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

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

Can I rate-limit list_persons? +

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

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

list_persons is provided by the Huly MCP server (dugynoo/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 218 Huly tools →

Across the catalogue

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

Guides

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