verify_account

Exchange the emailed 6-digit code for the account’s API key. Show the key to the user and tell them to configure it as the Bearer token for this MCP server.

SERVER3dassets SOURCE3dassets-mcp

Low RISK CLASS

Category Read

Parameters 22 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/3dassets-mcp/verify-account.md

WHAT IT DOES

What verify_account does on 3dassets

AI agents call verify_account to retrieve information from 3dassets without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`code`	string	Yes
`email`	string	Yes

Parameters from the server's own tool schema.

RISK

Why verify_account is rated Low

Even though verify_account only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signalsAccepts freeform code/query input (code)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs verify_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 verify_account, this is the rule to start with:

verify_account Allowed

verify_account is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "verify_account": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect 3dassets, apply this rule, and every verify_account call is checked against it from then on.

FAQ

Questions about verify_account

What does the verify_account tool do? +

Exchange the emailed 6-digit code for the account’s API key. Show the key to the user and tell them to configure it as the Bearer token for this MCP server. It is categorised as a Read tool in the 3dassets MCP Server, which means it retrieves data without modifying state.

What parameters does verify_account accept? +

verify_account accepts 2 parameters: code, email. Required: code, email. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on verify_account? +

Register the 3dassets MCP server in PolicyLayer and add a rule for verify_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.

What risk level is verify_account? +

verify_account is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit verify_account? +

Yes. Add a rate_limit block to the verify_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.

How do I block verify_account completely? +

Set action: deny in the PolicyLayer policy for verify_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.

What MCP server provides verify_account? +

verify_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.

KEEP EXPLORING

More on 3dassets, and thousands of servers like it.

This server

All 20 3dassets tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →