neuron_revoke_invitation
Revoke a pending organization invitation so it can no longer be accepted. This action cannot be undone.
This record as markdown: /tools/io-github-conquext-neuron/neuron-revoke-invitation.md
What neuron_revoke_invitation does on Neuron
AI agents call neuron_revoke_invitation to permanently remove resources in Neuron, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
orgId | string | Yes | Unique identifier (UUID) of the organization |
invitationId | string | Yes | Unique identifier (UUID) of the invitation to revoke |
Parameters from the server's own tool schema.
Why neuron_revoke_invitation is rated Critical
Revoking a pending invitation irreversibly destroys or invalidates organizational access that was previously granted. The description's explicit warning that the action 'cannot be undone' places this firmly in the Destructive category rather than Write, as it permanently eliminates a resource/state rather than merely modifying it.
From the tool's definition Tool description explicitly states 'This action cannot be undone' and uses the verb 'Revoke' to describe cancellation of a pending invitation with permanent effect.
Attacks that exploit this kind of access
The rule that runs neuron_revoke_invitation safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Neuron, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For neuron_revoke_invitation, this is the rule to start with:
neuron_revoke_invitation 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 Neuron, apply this rule, and every neuron_revoke_invitation call is checked against it from then on.
Questions about neuron_revoke_invitation
Revoke a pending organization invitation so it can no longer be accepted. This action cannot be undone. It is categorised as a Destructive tool in the Neuron MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
neuron_revoke_invitation accepts 2 parameters: orgId, invitationId. Required: orgId, invitationId. The full parameter table on this page comes from the server's own tool schema.
Register the Neuron MCP server in PolicyLayer and add a rule for neuron_revoke_invitation: 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 Neuron. Nothing to install.
neuron_revoke_invitation 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 neuron_revoke_invitation 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 neuron_revoke_invitation. 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.
neuron_revoke_invitation is provided by the Neuron MCP server (neuron-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Neuron, and thousands of servers like it.
Across the catalogue