Creates a new invitation for the given email address and sends the invitation email. Keep in mind that you cannot create an invitation if there is already one for the given email address. Also, trying to create an invitation for an email address that already exists in your application will result...
Risk signalsHandles credentials or secrets (auth) · Accepts raw HTML/template content (body) · Accepts URL/endpoint input (body.redirect_url) · High parameter count (10 properties)
Part of the Clerk server.
Free to start. No card required.
AI agents use CreateInvitation to create or modify resources in Clerk. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call CreateInvitation repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Clerk.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"CreateInvitation": {
"limits": [
{
"counter": "createinvitation_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Clerk policy for all 14 tools.
These attack patterns abuse exactly the kind of access CreateInvitation gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Creates a new invitation for the given email address and sends the invitation email. Keep in mind that you cannot create an invitation if there is already one for the given email address. Also, trying to create an invitation for an email address that already exists in your application will result to an error.. It is categorised as a Write tool in the Clerk MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Clerk MCP server in PolicyLayer and add a rule for CreateInvitation: 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 Clerk. Nothing to install.
CreateInvitation 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 CreateInvitation 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 CreateInvitation. 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.
CreateInvitation is provided by the Clerk MCP server (@clerk/clerk-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 14 Clerk tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.