This record as markdown: /tools/0xreisearch-crypto-mcp-beta/get-hacks.md
What get_hacks does on REI Crypto MCP Server
AI agents call get_hacks to retrieve information from REI Crypto 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_hacks is rated Low
This tool retrieves historical hack/exploit data from crypto security databases (likely Arkham Intelligence). It performs a simple query with no side effects, no code execution, no data modification, and no financial transactions. The information retrieved could inform risk assessments, but the tool itself only reads data.
From the tool's definition Tool name 'get_hacks' and endpoint 'GET /api/hacks' indicate a read-only retrieval operation. The GET HTTP method and 'get_' prefix confirm data retrieval without modification.
Attacks that exploit this kind of access
The rule that runs get_hacks safely
PolicyLayer is an MCP gateway: it sits between your AI agents and REI Crypto MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_hacks, this is the rule to start with:
get_hacks 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 REI Crypto MCP Server, apply this rule, and every get_hacks call is checked against it from then on.
Questions about get_hacks
GET /api/hacks. It is categorised as a Read tool in the REI Crypto MCP Server MCP Server, which means it retrieves data without modifying state.
Register the REI Crypto MCP Server MCP server in PolicyLayer and add a rule for get_hacks: 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 REI Crypto MCP Server. Nothing to install.
get_hacks 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_hacks 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_hacks. 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_hacks is provided by the REI Crypto MCP Server MCP server (0xreisearch/crypto-mcp-beta). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on REI Crypto MCP Server, and thousands of servers like it.
This server
Across the catalogue