Invite a new user to Devici
AI agents use invite_user to create or update resources in Devici MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Devici MCP Server environment.
This tool creates or modifies user access/membership data by inviting a new user. While it doesn't delete data (Destructive), execute arbitrary code (Execute), or move money (Financial), it does create a new entity in the system. The severity is medium because inviting unauthorized users could grant unintended access to threat models and security data, but the action is reversible (users can be removed).
From the tool's definition Tool name 'invite_user' and description 'Invite a new user to Devici' indicate the tool creates a new user account or invites a user, which is a reversible write operation that modifies the user roster.
Attacks that exploit this kind of access
Invite a new user to Devici. It is categorised as a Write tool in the Devici MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Devici MCP Server MCP server in PolicyLayer and add a rule for invite_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 Devici MCP Server. Nothing to install.
invite_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_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_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_user is provided by the Devici MCP Server MCP server (sdelements/devici-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →