get_users

THE RISK

Low Risk

Why get_users needs a policy

This tool performs a read operation that fetches user information from the HUDU platform. While it carries medium severity due to potential exposure of sensitive user data (names, roles, contact information), it is purely retrievals with no destructive, financial, or code execution capabilities. The blast radius is limited to information disclosure rather than system compromise or data loss.

From the tool's definition Tool name 'get_users' and description 'Retrieve users from HUDU' indicate a read-only operation that queries user data without modification. The verb 'Retrieve' explicitly signals data retrieval with no side effects.

Documented attack patterns abuse exactly the kind of access get_users gives an agent:

POLICY

How to control get_users

PolicyLayer is an MCP gateway — it sits between your AI agents and HUDU MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_users:

policy.json

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

get_users is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register HUDU MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More HUDU MCP Server tools

Read get_activity_logs Retrieve activity logs with advanced filtering options Read get_article Get detailed content of a specific article Read get_asset_layout Get detailed information about a specific asset layout Read get_asset_layouts Retrieve asset layouts from HUDU Read get_asset_passwords Retrieve password assets (credentials) for a company Read get_assets Retrieve assets with advanced filtering options Read get_companies Retrieve a list of companies/customers with advanced filtering options Read get_company_details Get detailed information about a specific company

All 17 HUDU MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_users

What does the get_users tool do? +

Retrieve users from HUDU. It is categorised as a Read tool in the HUDU MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_users? +

Register the HUDU MCP Server MCP server in PolicyLayer and add a rule for get_users: 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 HUDU MCP Server. Nothing to install.

What risk level is get_users? +

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

Can I rate-limit get_users? +

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

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

get_users is provided by the HUDU MCP Server MCP server (jlbyh2o/hudu-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every HUDU MCP Server tool call.

Start from HUDU MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →