get_user_earnings
Get a detailed earnings breakdown for a 3Dawn creator:
This record as markdown: /tools/3dawn-mcp/get-user-earnings.md
What get_user_earnings does on 3dawn
AI agents call get_user_earnings 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_user_earnings is rated Low
This is a Read operation: it retrieves financial information (earnings data) but does not move money, create transactions, or modify any state. While the data is financial in nature, the tool itself only reads/queries it. Severity is low because unauthorized access to a creator's earnings breakdown is a privacy/confidentiality concern rather than a direct financial loss or irreversible action risk.
From the tool's definition The tool name and description indicate it 'Get[s] a detailed earnings breakdown' — a retrieval operation with no side effects. It queries earnings data for display purposes.
Attacks that exploit this kind of access
The rule that runs get_user_earnings 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_user_earnings, this is the rule to start with:
get_user_earnings 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_user_earnings call is checked against it from then on.
Questions about get_user_earnings
Get a detailed earnings breakdown for a 3Dawn creator:. 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_user_earnings: 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_user_earnings 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_user_earnings 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_user_earnings. 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_user_earnings 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