Low Risk

get_earnings

Get your bounty earnings history. Shows amounts, currency, dates, and which programs paid out.

How to control get_earnings ↓

AI agents call get_earnings to retrieve information from HackerOne MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool retrieves and displays past earnings data (amounts, currency, dates, program sources) without modifying, creating, deleting, or executing any actions. It is purely informational read access to the user's own financial history.

From the tool's definition Tool name 'get_earnings' and description 'Get your bounty earnings history. Shows amounts, currency, dates, and which programs paid out' indicate retrieval of financial transaction history with no modification capability.

Documented attack patterns abuse exactly the kind of access get_earnings gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and HackerOne MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_earnings:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_earnings": {}
  }
}

get_earnings is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register HackerOne MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_earnings tool do? +

Get your bounty earnings history. Shows amounts, currency, dates, and which programs paid out. It is categorised as a Read tool in the HackerOne MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_earnings? +

Register the HackerOne MCP Server MCP server in PolicyLayer and add a rule for get_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 HackerOne MCP Server. Nothing to install.

What risk level is get_earnings? +

get_earnings is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_earnings? +

Yes. Add a rate_limit block to the get_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.

How do I block get_earnings completely? +

Set action: deny in the PolicyLayer policy for get_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.

What MCP server provides get_earnings? +

get_earnings is provided by the HackerOne MCP Server MCP server (sicks3c/hackerone-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every HackerOne MCP Server tool call.

Deterministic rules across all 16 HackerOne MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

16 HackerOne MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.