Withdraw/close one of your own HackerOne reports. Sends a close request with an optional message.
AI agents use close_report to create or update resources in HackerOne MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your HackerOne MCP Server environment.
Closing a report is a reversible write operation that changes the state of a security report. While it modifies data, it does not permanently delete the report or prevent reopening, distinguishing it from a Destructive action. The operation affects only the user's own reports, limiting blast radius to medium severity.
From the tool's definition Tool description explicitly states it can 'Withdraw/close one of your own HackerOne reports' and 'Sends a close request with an optional message.' This is a state-changing operation that modifies report status.
Documented attack patterns abuse exactly the kind of access close_report 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 close_report:
{
"version": "1",
"default": "deny",
"tools": {
"close_report": {
"limits": [
{
"counter": "close_report_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}close_report stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Withdraw/close one of your own HackerOne reports. Sends a close request with an optional message. It is categorised as a Write tool in the HackerOne MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the HackerOne MCP Server MCP server in PolicyLayer and add a rule for close_report: 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.
close_report is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the close_report 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 close_report. 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.
close_report 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.
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.