create_account
Create a contributor account for the user. Needs only a username and email. There is no password anywhere in this product, so never ask the user for one. A 6-digit code is emailed to them; ask the user to read it to you, then call verify_account to receive their API key. Only do this with the use...
This record as markdown: /tools/3dassets-mcp/create-account.md
What create_account does on 3dassets
AI agents use create_account to create or update resources in 3dassets, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 3dassets environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | — | Optional display name shown on assets; defaults to the username |
email | string | Yes | |
website | string | — | |
username | string | Yes | Public handle, lowercase letters/numbers/hyphens |
Parameters from the server's own tool schema.
Why create_account is rated Medium
An AI agent can call create_account faster than any human can review: one bad instruction and it creates or modifies resources in 3dassets by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs create_account safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 3dassets, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_account, this is the rule to start with:
create_account 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 3dassets, apply this rule, and every create_account call is checked against it from then on.
Questions about create_account
Create a contributor account for the user. Needs only a username and email. There is no password anywhere in this product, so never ask the user for one. A 6-digit code is emailed to them; ask the user to read it to you, then call verify_account to receive their API key. Only do this with the user’s explicit consent. It is categorised as a Write tool in the 3dassets MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_account accepts 4 parameters: name, email, website, username. Required: email, username. The full parameter table on this page comes from the server's own tool schema.
Register the 3dassets MCP server in PolicyLayer and add a rule for create_account: 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 3dassets. Nothing to install.
create_account 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_account 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_account. 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_account is provided by the 3dassets MCP server (3dassets-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 3dassets, and thousands of servers like it.
This server
Across the catalogue