get_asset_details
Get full details for a specific 3D asset by its numeric ID.
This record as markdown: /tools/3dawn-mcp/get-asset-details.md
What get_asset_details does on 3dawn
AI agents call get_asset_details to retrieve information from 3dawn without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_asset_details is rated Low
This tool queries and returns information about a 3D asset—a read-only operation. The verb 'get' and the lack of any mention of modification, deletion, or execution confirms it belongs in the Read category. The severity is low because retrieving asset metadata poses minimal risk to the system or user data.
From the tool's definition Tool name 'get_asset_details' and description 'Get full details for a specific 3D asset' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs get_asset_details safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 3dawn, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_asset_details, this is the rule to start with:
get_asset_details 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 3dawn, apply this rule, and every get_asset_details call is checked against it from then on.
Questions about get_asset_details
Get full details for a specific 3D asset by its numeric ID. It is categorised as a Read tool in the 3dawn MCP Server, which means it retrieves data without modifying state.
Register the 3dawn MCP server in PolicyLayer and add a rule for get_asset_details: 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 3dawn. Nothing to install.
get_asset_details 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 get_asset_details 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 get_asset_details. 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.
get_asset_details is provided by the 3dawn MCP server (3DawnRH/3dawn-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 3dawn, and thousands of servers like it.
This server
Across the catalogue