invite_employee
Create or promote and invite an employee, or resend an inactive employee invitation. mode=create-or-promote requires the exact Huly display name and email; one checked atomic transaction creates or updates the Person, email SocialIdentity, and active Employee before sending. A changed authoritati...
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/invite-employee.md
What invite_employee does on Huly
AI agents use invite_employee 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 invite_employee is rated Medium
Creates and modifies employee records reversibly with organizational access implications; no financial or destructive component.
From the tool's definition Create or promote and invite an employee, atomically creates or updates Person, email SocialIdentity, and active Employee
Attacks that exploit this kind of access
The rule that runs invite_employee 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 invite_employee, this is the rule to start with:
invite_employee 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 invite_employee call is checked against it from then on.
Questions about invite_employee
Create or promote and invite an employee, or resend an inactive employee invitation. mode=create-or-promote requires the exact Huly display name and email; one checked atomic transaction creates or updates the Person, email SocialIdentity, and active Employee before sending. A changed authoritative precondition sends no invite and directs the caller to retry in a fresh session. mode=invite-existing requires an exact email/name locator and rejects active or non-Employee targets. Omitted role preserves the Employee role; an explicit different role is persisted atomically before resend. Returns no invitation link, credential, or token; an invitation-provider failure reports completed preparation. 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 invite_employee: 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.
invite_employee 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 invite_employee 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 invite_employee. 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.
invite_employee 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