listInvitations
List organisation invitations. Auth: org id must match the credential's organisation AND the credential must hold the can_manage_members capability. Status defaults to 'pending'. Pass 'all' to disable filtering.
This record as markdown: /tools/io-stablebaseline-sb/listinvitations.md
What listInvitations does on Stable Baseline
AI agents call listInvitations to retrieve information from Stable Baseline 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 |
|---|---|---|---|
limit | number | — | |
offset | number | — | |
status | string | — | |
organisation_id | string | Yes | Organisation UUID. Must match the credential's organisation. |
Parameters from the server's own tool schema.
Why listInvitations is rated Low
This tool queries and retrieves invitation records filtered by organisation and status. It performs no creation, modification, deletion, or execution of external operations. The authentication checks (org id match, can_manage_members capability) are access controls, not indicators of severity.
From the tool's definition Tool name is 'listInvitations' and description states it 'List organisation invitations' with filtering by status. The verb 'List' is explicitly a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs listInvitations safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Stable Baseline, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For listInvitations, this is the rule to start with:
listInvitations 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 Stable Baseline, apply this rule, and every listInvitations call is checked against it from then on.
Questions about listInvitations
List organisation invitations. Auth: org id must match the credential's organisation AND the credential must hold the can_manage_members capability. Status defaults to 'pending'. Pass 'all' to disable filtering. It is categorised as a Read tool in the Stable Baseline MCP Server, which means it retrieves data without modifying state.
listInvitations accepts 4 parameters: limit, offset, status, organisation_id. Required: organisation_id. The full parameter table on this page comes from the server's own tool schema.
Register the Stable Baseline MCP server in PolicyLayer and add a rule for listInvitations: 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 Stable Baseline. Nothing to install.
listInvitations 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 listInvitations 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 listInvitations. 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.
listInvitations is provided by the Stable Baseline MCP server (https://api.stablebaseline.io/functions/v1/cloud-serve/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Stable Baseline, and thousands of servers like it.
This server
Across the catalogue