invite_portal_user
Invite a new person into a portal: creates their account and mails the portal's invitation letter. The new account gets a password of its own, which only the invitation letter shows (with a one-time link that signs the person in); the answer's invitation says what was mailed. Never tell anyone a ...
This record as markdown: /tools/com-quintadb-mcp/invite-portal-user.md
What invite_portal_user does on QuintaDB
AI agents use invite_portal_user to create or update resources in QuintaDB, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your QuintaDB environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
email | string | Yes | Email юзера |
login | string | — | Логін (якщо не вказано — використовується email) |
app_id | string | Yes | Project ID (from list_projects) |
portal_id | string | Yes | Portal ID (from list_portals or describe_project) |
send_email | boolean | — | Mail the portal's invitation letter (default true). false: nobody is told a password — the person sets their own from the portal's sign-in page. |
Parameters from the server's own tool schema.
Why invite_portal_user is rated Medium
An AI agent can call invite_portal_user faster than any human can review: one bad instruction and it creates or modifies resources in QuintaDB by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs invite_portal_user safely
PolicyLayer is an MCP gateway: it sits between your AI agents and QuintaDB, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For invite_portal_user, this is the rule to start with:
invite_portal_user stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect QuintaDB, apply this rule, and every invite_portal_user call is checked against it from then on.
Questions about invite_portal_user
Invite a new person into a portal: creates their account and mails the portal's invitation letter. The new account gets a password of its own, which only the invitation letter shows (with a one-time link that signs the person in); the answer's invitation says what was mailed. Never tell anyone a password. It is categorised as a Write tool in the QuintaDB MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
invite_portal_user accepts 5 parameters: email, login, app_id, portal_id, send_email. Required: email, app_id, portal_id. The full parameter table on this page comes from the server's own tool schema.
Register the QuintaDB MCP server in PolicyLayer and add a rule for invite_portal_user: 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 QuintaDB. Nothing to install.
invite_portal_user is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the invite_portal_user 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 invite_portal_user. 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.
invite_portal_user is provided by the QuintaDB MCP server (https://quintadb.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on QuintaDB, and thousands of servers like it.
This server
Across the catalogue