get_demo

Get one demo: the pack, the spawn point, the walkable bounds, the points of interest, and every placement (public asset slug, position in metres, yaw in degrees) with the CDN URL and bounds of each model placed. Load the models with a plain GLTFLoader and apply the transforms to reproduce the scene.

SERVER3dassets SOURCE3dassets-mcp

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/3dassets-mcp/get-demo.md

WHAT IT DOES

What get_demo does on 3dassets

AI agents call get_demo 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
`slug`	string	Yes

Parameters from the server's own tool schema.

RISK

Why get_demo is rated Low

Even though get_demo 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 signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_demo Allowed

get_demo 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": {
    "get_demo": {}
  }
}

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 get_demo call is checked against it from then on.

FAQ

Questions about get_demo

What does the get_demo tool do? +

What parameters does get_demo accept? +

get_demo accepts 1 parameter: slug. Required: slug. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_demo? +

Register the 3dassets MCP server in PolicyLayer and add a rule for get_demo: 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 get_demo? +

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

Can I rate-limit get_demo? +

Yes. Add a rate_limit block to the get_demo 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 get_demo completely? +

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

get_demo 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

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

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