This record as markdown: /tools/launch-on-basis-mcp-ts/get-dev-total-earnings.md
What get_dev_total_earnings does on Basis MCP Server
AI agents call get_dev_total_earnings to retrieve information from Basis MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_dev_total_earnings is rated Low
The tool retrieves developer earnings data. This is a read-only query with no side effects, modifications, or execution risk. The incomplete description ('Get a dev') is minimal but the naming convention strongly indicates a simple data retrieval function.
From the tool's definition Tool name 'get_dev_total_earnings' indicates a retrieval operation ('get'). The prefix 'get_' is a read operation that queries data without modification.
Attacks that exploit this kind of access
The rule that runs get_dev_total_earnings safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Basis MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_dev_total_earnings, this is the rule to start with:
get_dev_total_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 Basis MCP Server, apply this rule, and every get_dev_total_earnings call is checked against it from then on.
Questions about get_dev_total_earnings
Get a dev. It is categorised as a Read tool in the Basis MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Basis MCP Server MCP server in PolicyLayer and add a rule for get_dev_total_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 Basis MCP Server. Nothing to install.
get_dev_total_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_dev_total_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_dev_total_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_dev_total_earnings is provided by the Basis MCP Server MCP server (launch-on-basis/mcp-ts). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Basis MCP Server, and thousands of servers like it.
This server
Across the catalogue