get_user_invite
Get one invitation by invite id and return its email, role, status, and expiry. Use this for pending invites only; use get_user for accepted users.
This record as markdown: /tools/codeswhat-portkey-admin-mcp/get-user-invite.md
What get_user_invite does on Portkey Admin
AI agents call get_user_invite 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 get_user_invite is rated Low
This tool queries and returns metadata about a pending user invitation. It performs a read-only operation that retrieves information about an invite (email, role, status, expiry) without creating, modifying, deleting, or executing any actions. No data is changed and no external operations are triggered.
From the tool's definition Tool name 'get_user_invite' and description states it retrieves invitation data ('Get one invitation by invite id and return its email, role, status, and expiry'). The verb 'Get' and 'return' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_user_invite 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 get_user_invite, this is the rule to start with:
get_user_invite 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 get_user_invite call is checked against it from then on.
Questions about get_user_invite
Get one invitation by invite id and return its email, role, status, and expiry. Use this for pending invites only; use get_user for accepted users. 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 get_user_invite: 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.
get_user_invite 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 get_user_invite 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 get_user_invite. 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.
get_user_invite 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