list_hr_request_types

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-hr-request-types.md

WHAT IT DOES

What list_hr_request_types does on Huly

AI agents call list_hr_request_types 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_hr_request_types is rated Low

Tool retrieves HR request type definitions without modifying data or triggering external operations.

From the tool's definition Discover installed HR request types by stable ID and Huly-translated human label.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

list_hr_request_types Allowed

list_hr_request_types 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_hr_request_types": {}
  }
}

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

FAQ

Questions about list_hr_request_types

What does the list_hr_request_types tool do? +

Discover installed HR request types by stable ID and Huly-translated human label. Set locale to a supported Huly locale such as fr; labels from any supported locale may be used by request tools, while ambiguous labels are rejected. Request-type mutation is intentionally unsupported because Huly installs these as model-space documents and exposes no stable runtime mutation contract. 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_hr_request_types? +

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

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

Can I rate-limit list_hr_request_types? +

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

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

list_hr_request_types 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 600 Huly tools →

Across the catalogue

list_symbols on ACE-MCP →aiva_list_affiliates on AIVA MCP Server → The MCP Attack Database →

Guides

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