Create a random test user in the local database. Generates a unique email + bcrypt password hash and inserts via docker exec. Creates a demo project if the project uses multi-tenancy.
AI agents use cli_dev_add_user to create or update resources in LaunchFrame MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your LaunchFrame MCP environment.
This tool creates new records (a test user and potentially a demo project) in a local development database. The operations are reversible (users can be deleted), and the scope is limited to local development environments. While it modifies data, it does not irreversibly delete anything, execute arbitrary code, or trigger production changes. It qualifies as Write.
From the tool's definition Tool description states it "Create[s] a random test user in the local database" and "inserts via docker exec". These are create operations that modify database state reversibly.
Attacks that exploit this kind of access
Create a random test user in the local database. Generates a unique email + bcrypt password hash and inserts via docker exec. Creates a demo project if the project uses multi-tenancy. It is categorised as a Write tool in the LaunchFrame MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the LaunchFrame MCP server in PolicyLayer and add a rule for cli_dev_add_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 LaunchFrame MCP. Nothing to install.
cli_dev_add_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 cli_dev_add_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 cli_dev_add_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.
cli_dev_add_user is provided by the LaunchFrame MCP server (launchframe-dev/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 →