AI agents use create_user to create or update resources in Kula Ai — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kula Ai environment.
This tool creates a new user entity in the system, which is a reversible write operation (the user record and invitation can be removed or the invitation can be revoked). It does not delete, execute arbitrary code, move money, or destroy data.
From the tool's definition Tool description states 'Invite a new user to the account. The user is created in the pending state and sent an invitation email.' This creates a new user record and triggers an email action.
Attacks that exploit this kind of access
Invite a new user to the account. The user is created in the pending state and sent an invitation email. Requires email and first_name. It is categorised as a Write tool in the Kula Ai MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Kula Ai MCP server in PolicyLayer and add a rule for create_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 Kula Ai. Nothing to install.
create_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 create_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 create_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.
create_user is provided by the Kula Ai MCP server (kula-ai/kula-mcp-server). 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 →