list_recruiting_vacancy_types
List Huly Recruiting vacancy workflow types. Use the returned type ID or exact type name in create_recruiting_vacancy. Defaults vacancy creation to Huly
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/list-recruiting-vacancy-types.md
What list_recruiting_vacancy_types does on Huly
AI agents call list_recruiting_vacancy_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.
Why list_recruiting_vacancy_types is rated Low
This is a pure query operation that retrieves and enumerates existing data (vacancy types). It has no side effects, makes no modifications, and does not execute external operations. The word 'list' is a hallmark Read category operation. The tool is explicitly informational, returning reference data to be used by other tools (create_recruiting_vacancy).
From the tool's definition Tool name is 'list_recruiting_vacancy_types' which explicitly lists/retrieves vacancy workflow types. Description states 'List Huly Recruiting vacancy workflow types' with no mutation language like create, update, delete, or execute.
Attacks that exploit this kind of access
The rule that runs list_recruiting_vacancy_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_recruiting_vacancy_types, this is the rule to start with:
list_recruiting_vacancy_types is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Huly, apply this rule, and every list_recruiting_vacancy_types call is checked against it from then on.
Questions about list_recruiting_vacancy_types
List Huly Recruiting vacancy workflow types. Use the returned type ID or exact type name in create_recruiting_vacancy. Defaults vacancy creation to Huly. It is categorised as a Read tool in the Huly MCP Server, which means it retrieves data without modifying state.
Register the Huly MCP server in PolicyLayer and add a rule for list_recruiting_vacancy_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.
list_recruiting_vacancy_types is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_recruiting_vacancy_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.
Set action: deny in the PolicyLayer policy for list_recruiting_vacancy_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.
list_recruiting_vacancy_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.
More on Huly, and thousands of servers like it.
This server
Across the catalogue