get_embed_analytics
Get view count and earnings analytics for a 3D asset's embed.
This record as markdown: /tools/3dawn-mcp/get-embed-analytics.md
What get_embed_analytics does on 3dawn
AI agents call get_embed_analytics 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_embed_analytics is rated Low
This tool retrieves read-only analytics data (view counts and earnings information) about an embedded 3D asset. There are no side effects, no data modification, no code execution, and no destructive operations. It is a straightforward query operation with minimal blast radius if misused by an AI agent—worst case being access to analytics data the user may not have intended to expose.
From the tool's definition Tool name 'get_embed_analytics' and description 'Get view count and earnings analytics' indicate data retrieval with no modification, deletion, or code execution. It queries analytics metrics for an existing asset.
Attacks that exploit this kind of access
The rule that runs get_embed_analytics 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_embed_analytics, this is the rule to start with:
get_embed_analytics 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_embed_analytics call is checked against it from then on.
Questions about get_embed_analytics
Get view count and earnings analytics for a 3D asset's embed. 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_embed_analytics: 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_embed_analytics 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_embed_analytics 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_embed_analytics. 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_embed_analytics 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