Low Risk

search_reports

Search and list your HackerOne reports. Filter by keyword, program, severity, or state. Great for finding past reports to reference when drafting new ones.

How to control search_reports ↓

AI agents call search_reports 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 queries existing report data without creating, modifying, deleting, or executing operations. Filtering and searching are classic read operations. The blast radius of misuse is low—an agent could only retrieve reports already accessible to the user, posing minimal risk.

From the tool's definition Tool description explicitly states 'Search and list your HackerOne reports' and 'Filter by keyword, program, severity, or state.' The verb 'search and list' combined with filtering parameters indicates data retrieval with no modification.

Documented attack patterns abuse exactly the kind of access search_reports 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 search_reports:

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

search_reports 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 search_reports tool do? +

Search and list your HackerOne reports. Filter by keyword, program, severity, or state. Great for finding past reports to reference when drafting new ones. 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 search_reports? +

Register the HackerOne MCP Server MCP server in PolicyLayer and add a rule for search_reports: 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 search_reports? +

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

Can I rate-limit search_reports? +

Yes. Add a rate_limit block to the search_reports 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 search_reports completely? +

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

search_reports 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.