invite_user
Use this when the user wants to invite a new person to the organization. The invitation email is sent immediately. Omitted roleId defaults to Support User. The email domain must be permitted by the customer's invitation policy; existing users and pending invitees cannot be re-invited. Do NOT use ...
This record as markdown: /tools/doit/invite-user.md
What invite_user does on Doit
AI agents use invite_user to create or update resources in Doit, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Doit environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
email | string | Yes | The email address of the user to invite (required). Its domain must be permitted by the customer's invitation policy; existing users and pending invitees cannot |
roleId | string | — | The role ID from list_roles to assign to the invited user. Omission defaults to Support User. |
organizationId | string | — | The ID of the organization to assign the invited user to. |
Parameters from the server's own tool schema.
Why invite_user is rated Medium
An AI agent can call invite_user faster than any human can review: one bad instruction and it creates or modifies resources in Doit by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs invite_user safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Doit, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For invite_user, this is the rule to start with:
invite_user 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 Doit, apply this rule, and every invite_user call is checked against it from then on.
Questions about invite_user
Use this when the user wants to invite a new person to the organization. The invitation email is sent immediately. Omitted roleId defaults to Support User. The email domain must be permitted by the customer's invitation policy; existing users and pending invitees cannot be re-invited. Do NOT use this for updating existing users (use update_user) or listing users (use list_users). It is categorised as a Write tool in the Doit MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
invite_user accepts 3 parameters: email, roleId, organizationId. Required: email. The full parameter table on this page comes from the server's own tool schema.
Register the Doit MCP server in PolicyLayer and add a rule for invite_user: 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 Doit. Nothing to install.
invite_user 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_user 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_user. 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_user is provided by the Doit MCP server (@doitintl/doit-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Doit, and thousands of servers like it.
This server
Across the catalogue