create_recruiting_vacancy
Create a Recruiting vacancy like the Huly UI: increments the vacancy sequence, stores fullDescription as markdown-backed collaborative markup, defaults members/owners to the current account, and creates vacancy type-data mixin {}.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/create-recruiting-vacancy.md
What create_recruiting_vacancy does on Huly
AI agents use create_recruiting_vacancy to create or update resources in Huly, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Huly environment.
Why create_recruiting_vacancy is rated Medium
This tool creates new recruiting vacancy records in the Huly system, which is a reversible data creation operation (Write category). It does not execute arbitrary code, delete data, or move money.
From the tool's definition Tool description states 'Create a Recruiting vacancy' and 'stores fullDescription' and 'creates vacancy type-data mixin', indicating creation and storage of new data records.
Attacks that exploit this kind of access
The rule that runs create_recruiting_vacancy 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 create_recruiting_vacancy, this is the rule to start with:
create_recruiting_vacancy stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 create_recruiting_vacancy call is checked against it from then on.
Questions about create_recruiting_vacancy
Create a Recruiting vacancy like the Huly UI: increments the vacancy sequence, stores fullDescription as markdown-backed collaborative markup, defaults members/owners to the current account, and creates vacancy type-data mixin {}. It is categorised as a Write tool in the Huly MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Huly MCP server in PolicyLayer and add a rule for create_recruiting_vacancy: 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.
create_recruiting_vacancy is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_recruiting_vacancy 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 create_recruiting_vacancy. 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.
create_recruiting_vacancy 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