organizations_list_invitations
Read organizations.list-invitations through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/organizations-list-invitations.md
What organizations_list_invitations does on Appaloft
AI agents call organizations_list_invitations to retrieve information from Appaloft 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 | integer | — | |
cursor | string | — | |
status | string | — | |
organizationId | string | Yes |
Parameters from the server's own tool schema.
Why organizations_list_invitations is rated Low
This tool retrieves and queries invitation data for organizations. The description's use of 'Read' and 'list' (a retrieval operation) indicates no data creation, modification, deletion, or execution of arbitrary operations. The blast radius of misuse is limited to information disclosure about pending invitations, which is low-severity.
From the tool's definition Tool description explicitly states 'Read organizations.list-invitations' and the verb 'list-invitations' retrieves organizational invitation data without modification or side effects.
Attacks that exploit this kind of access
The rule that runs organizations_list_invitations safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Appaloft, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For organizations_list_invitations, this is the rule to start with:
organizations_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 Appaloft, apply this rule, and every organizations_list_invitations call is checked against it from then on.
Questions about organizations_list_invitations
Read organizations.list-invitations through the Appaloft application operation catalog. Shared with CLI and HTTP/API. It is categorised as a Read tool in the Appaloft MCP Server, which means it retrieves data without modifying state.
organizations_list_invitations accepts 4 parameters: limit, cursor, status, organizationId. Required: organizationId. The full parameter table on this page comes from the server's own tool schema.
Register the Appaloft MCP server in PolicyLayer and add a rule for organizations_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 Appaloft. Nothing to install.
organizations_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 organizations_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 organizations_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.
organizations_list_invitations is provided by the Appaloft MCP server (@appaloft/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Appaloft, and thousands of servers like it.
This server
Across the catalogue