list_user_statuses

List Huly user presence records — who is currently online, with their account UUID and last status change timestamp. Filter by

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-user-statuses.md

WHAT IT DOES

What list_user_statuses does on Huly

AI agents call list_user_statuses 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_user_statuses is rated Low

This tool queries and returns user presence information (online status, UUIDs, timestamps). It is a read-only operation that retrieves data without creating, modifying, deleting, executing code, or affecting financial systems. The only potential concern is minor privacy sensitivity around user presence, but the impact is informational only.

From the tool's definition Tool name 'list_user_statuses' and description 'List Huly user presence records — who is currently online, with their account UUID and last status change timestamp' indicate retrieval of presence/status data without modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

list_user_statuses Allowed

list_user_statuses 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_user_statuses": {}
  }
}

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

FAQ

Questions about list_user_statuses

What does the list_user_statuses tool do? +

List Huly user presence records — who is currently online, with their account UUID and last status change timestamp. Filter by. 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_user_statuses? +

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

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

Can I rate-limit list_user_statuses? +

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

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

list_user_statuses 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 →