list_demos
List the walkable demo scenes staff have built from single packs. Each is a small environment a person can walk through on the site and an agent can load as a layout. Use get_demo for the placements.
This record as markdown: /tools/3dassets-mcp/list-demos.md
What list_demos does on 3dassets
AI agents call list_demos 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.
Why list_demos is rated Low
Even though list_demos 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.
Attacks that exploit this kind of access
The rule that runs list_demos 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 list_demos, this is the rule to start with:
list_demos is read-only, so it stays allowed. 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 list_demos call is checked against it from then on.
Questions about list_demos
List the walkable demo scenes staff have built from single packs. Each is a small environment a person can walk through on the site and an agent can load as a layout. Use get_demo for the placements. It is categorised as a Read tool in the 3dassets MCP Server, which means it retrieves data without modifying state.
Register the 3dassets MCP server in PolicyLayer and add a rule for list_demos: 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.
list_demos is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_demos 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 list_demos. 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.
list_demos 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