// SCAN REPORT

Reversecore_MCP

43 tools. 19 can modify or destroy data without limits.

19 write tools that can modify data. Rate limits recommended.

Last updated: 27 Jun 2026

19 can modify or destroy data

24 read-only

43 tools total

Community server · catalogue entry verified 27/06/2026

How to control Reversecore_MCP ↓

TOOL MAP

What Reversecore_MCP exposes to your agents

Read (24) Write / Execute (19) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Reversecore_MCP tools

Execute · High Radare2_decompile_function Radare2's decompile function operation runs analysis/decompilation commands against a binary target. Execute · Critical Radare2_run_command This tool permits execution of arbitrary Radare2 commands, which can range from read-only analysis to system calls, code execution, and binary modification. Execute · High Radare2_analyze Radare2 is a well-known binary analysis and reverse engineering framework. Execute · High Radare2_calculate Radare2 is a reverse engineering framework capable of executing expressions, evaluating code, and performing operations with side effects.

19 of Reversecore_MCP's 43 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Reversecore_MCP

PolicyLayer is an MCP gateway — it sits between your AI agents and Reversecore_MCP, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "complete_memory_session": {
    "limits": [
      {
        "counter": "complete_memory_session_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "find_similar_patterns": {
    "limits": [
      {
        "counter": "find_similar_patterns_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Reversecore_MCP — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON REVERSECORE_MCP →

Instant setup, no code required.

FULL CATALOGUE

All 43 Reversecore_MCP tools

EXECUTE 7 tools

Execute Radare2_analyze Radare2_analyze Execute Radare2_calculate Radare2_calculate Execute Radare2_decompile_function Radare2_decompile_function Execute Radare2_disassemble Radare2_disassemble Execute Radare2_disassemble_function Radare2_disassemble_function Execute Radare2_run_command Radare2_run_command Execute Radare2_use_decompiler Select which decompiler backend to use.

WRITE 12 tools

Write complete_memory_session complete_memory_session Write create_memory_session create_memory_session Write Radare2_close_file Close the currently open radare2 session for a file. Write Radare2_open_file Radare2_open_file Write Radare2_rename_flag Radare2_rename_flag Write Radare2_rename_function Rename the function at the specified address. Write Radare2_set_comment Add a comment at the specified address. Write Radare2_set_function_prototype Radare2_set_function_prototype Write resume_memory_session resume_memory_session Write save_memory_item save_memory_item Write save_pattern save_pattern Write update_memory_session_time update_memory_session_time

READ 24 tools

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Reversecore_MCP

How do I prevent bulk modifications through Reversecore_MCP? +

The Reversecore_MCP server has 12 write tools including complete_memory_session, create_memory_session, Radare2_close_file. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Reversecore_MCP.

How many tools does the Reversecore_ MCP server expose? +

43 tools across 4 categories: Destructive, Execute, Read, Write. 24 are read-only. 19 can modify, create, or delete data.

How do I enforce a policy on Reversecore_MCP? +

Register the Reversecore_ MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Reversecore_MCP tool call.

Deterministic rules across all 43 Reversecore_MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON REVERSECORE_MCP →

Instant setup, no code required.

43 Reversecore_MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.