cancel_invite
Manage users who have access to the DoiT platform. Marks the invite as Cancelled and invalidates the invite token so any outstanding email links stop working. The invite document is retained (soft cancel) — the user row remains visible in GET /iam/v1/users with inviteStatus: Cancelled. Use DELETE...
This record as markdown: /tools/doit/cancel-invite.md
What cancel_invite does on Doit
AI agents call cancel_invite to permanently remove resources in Doit, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | |
dryRun | boolean | — | |
Idempotency-Key | string | Yes | |
customerContext | string | — | Scope the request to a specific customer by ID. Required for DoiT employees (whose token isn't tied to a single customer); omit for direct customer users. |
Parameters from the server's own tool schema.
Why cancel_invite is rated Critical
An AI agent that decides to call cancel_invite doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Doit is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs cancel_invite 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 cancel_invite, this is the rule to start with:
cancel_invite is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Doit, apply this rule, and every cancel_invite call is checked against it from then on.
Questions about cancel_invite
Manage users who have access to the DoiT platform. Marks the invite as Cancelled and invalidates the invite token so any outstanding email links stop working. The invite document is retained (soft cancel) — the user row remains visible in GET /iam/v1/users with inviteStatus: Cancelled. Use DELETE /iam/v1/users/{id} to fully remove the record. Returns 404 if no invite exists for the given ID, and 409 if the invite is already cancelled. Requires usersManager permission. It is categorised as a Destructive tool in the Doit MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
cancel_invite accepts 4 parameters: id, dryRun, Idempotency-Key, customerContext. Required: id, Idempotency-Key. 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 cancel_invite: 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.
cancel_invite is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the cancel_invite 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 cancel_invite. 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.
cancel_invite 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.
Across the catalogue