list_user_invites
List pending and sent invitations with id, email, role, status, and expiry. Use this to check invite state; use list_all_users for users who already accepted.
This record as markdown: /tools/codeswhat-portkey-admin-mcp/list-user-invites.md
What list_user_invites does on Portkey Admin
AI agents call list_user_invites to retrieve information from Portkey Admin without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_user_invites is rated Low
This tool queries and retrieves invitation data (id, email, role, status, expiry) without creating, modifying, deleting, or executing any operations. It is a pure read operation on existing invitation records with no capability to change state or trigger external actions. Low severity reflects minimal blast radius if an agent lists invitations—information disclosure is the only risk.
From the tool's definition Tool name is 'list_user_invites' and description states it 'List[s] pending and sent invitations' — a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs list_user_invites safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Portkey Admin, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_user_invites, this is the rule to start with:
list_user_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 Portkey Admin, apply this rule, and every list_user_invites call is checked against it from then on.
Questions about list_user_invites
List pending and sent invitations with id, email, role, status, and expiry. Use this to check invite state; use list_all_users for users who already accepted. It is categorised as a Read tool in the Portkey Admin MCP Server, which means it retrieves data without modifying state.
Register the Portkey Admin MCP server in PolicyLayer and add a rule for list_user_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 Portkey Admin. Nothing to install.
list_user_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 list_user_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 list_user_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.
list_user_invites is provided by the Portkey Admin MCP server (codeswhat/portkey-admin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Portkey Admin, and thousands of servers like it.
This server
Across the catalogue