codex_list_invites
List pending invitations in the organization
This record as markdown: /tools/sagemcp-sagemcp/codex-list-invites.md
What codex_list_invites does on Sage MCP
AI agents call codex_list_invites to retrieve information from Sage MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why codex_list_invites is rated Low
This tool retrieves and displays existing invitation data from the organization. It has no side effects—it does not create, modify, delete, or execute any actions. The blast radius of misuse is minimal; an unauthorized user could view pending invitations but cannot alter them or take destructive actions. Classified as Read with low severity.
From the tool's definition Tool name and description indicate 'List pending invitations' - a retrieval operation that queries organization data without modifying or deleting anything. The verb 'list' is characteristic of Read operations.
Attacks that exploit this kind of access
The rule that runs codex_list_invites safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sage MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For codex_list_invites, this is the rule to start with:
codex_list_invites 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 Sage MCP, apply this rule, and every codex_list_invites call is checked against it from then on.
Questions about codex_list_invites
List pending invitations in the organization. It is categorised as a Read tool in the Sage MCP MCP Server, which means it retrieves data without modifying state.
Register the Sage MCP server in PolicyLayer and add a rule for codex_list_invites: 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 Sage MCP. Nothing to install.
codex_list_invites 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 codex_list_invites 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 codex_list_invites. 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.
codex_list_invites is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sage, and thousands of servers like it.
This server
Across the catalogue