neuron_list_invitations
Retrieve a list of all pending invitations for the organization that have not yet been accepted or revoked.
This record as markdown: /tools/io-github-conquext-neuron/neuron-list-invitations.md
What neuron_list_invitations does on Neuron
AI agents call neuron_list_invitations to retrieve information from Neuron without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
orgId | string | Yes | Unique identifier (UUID) of the organization |
Parameters from the server's own tool schema.
Why neuron_list_invitations is rated Low
This tool queries and returns invitation data without modifying, executing, or deleting anything. It is a straightforward read operation with minimal security risk, as it provides visibility into pending invitations within the organization.
From the tool's definition Tool name and description: 'Retrieve a list of all pending invitations' — the verb 'Retrieve' and the read-only nature of listing invitations (no state changes, no side effects) clearly indicate a data retrieval operation.
Attacks that exploit this kind of access
The rule that runs neuron_list_invitations 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_list_invitations, this is the rule to start with:
neuron_list_invitations is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Neuron, apply this rule, and every neuron_list_invitations call is checked against it from then on.
Questions about neuron_list_invitations
Retrieve a list of all pending invitations for the organization that have not yet been accepted or revoked. It is categorised as a Read tool in the Neuron MCP Server, which means it retrieves data without modifying state.
neuron_list_invitations accepts 1 parameter: orgId. Required: orgId. 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_list_invitations: 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_list_invitations is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the neuron_list_invitations 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_list_invitations. 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_list_invitations 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.
This server
Across the catalogue