Users Report Claude Triggers Safety Classifier Mid Response When Asked to Use Reverse Engineer Anything MCP Tool
Anthropic may have just klled REA. Users are reporting that Claude now hits a safety check when asked to use REA (Reverse Engineer Anything) for detailed reverse-engineering work, even after completing the research. REA itself is an open-source MCP tool that lets AI coding agents inspect software locally, trace how features work, and use that information to build compatible implementations
Context
Mid response safety blocks on local software inspection workflows highlight growing friction between AI lab cyber defense guardrails and developers using open source MCP tools for interoperability and privacy audits.
Reverse Engineer Anything, known as REA and published on GitHub under morluto/rea, is an MIT licensed open source MCP server that connects coding agents to local binary and application analysis tools such as Ghidra, Hopper, IDA, and V8 Inspector. The tool gained rapid traction on GitHub in October 2026 as developers used it with Claude Code and other agents to inspect compiled desktop apps, Electron packages, and device firmware. Earlier in the week, viral posts documented researchers using AI assisted reverse engineering to inspect 2025 Samsung smart TV firmware and telemetry services.
Deep dive
According to user reports circulating on Reddit and X, Anthropic's Claude has begun halting responses with a safety check when prompted to generate detailed reverse engineering playbooks or analysis with REA, the open source Reverse Engineer Anything MCP server. The reports originated from a post on the r/claude subreddit by user Clair_Personality, shared on X by security researcher 0x0SojalSec and summarized by Pirat_Nation. In the screenshots shared by users, Claude completes the initial search or tool calls before an output classifier interrupts the session and states that a safety check stopped the response partway through creating the playbook.
In a second screenshot from the same thread, Claude states that an earlier session's attempt to write the document was stopped by a safety classifier and that rewording or finishing the detailed writeup in a follow up turn is blocked to prevent bypassing the stop. Commentators including 0x0SojalSec noted that the reports followed viral threads earlier in the week by researcher log4j, who documented rooting a 2025 Samsung television to inspect its automatic content recognition and audio telemetry pipelines and later reported having an OpenAI account banned for cyber abuse.
These reports remain unconfirmed user accounts, and Anthropic has not issued any official statement announcing a policy change or specific restriction targeting REA. Meanwhile, REA creator morluto did not report a platform wide shutdown and posted on October 24 that REA version 6.8 will be released soon. Developers on X also noted that because REA runs locally as an open standard MCP server, users can connect the same inspection workflows to alternative coding agents and open weight models.
What to expect next
Developers and security researchers will watch whether Anthropic clarifies how its cyber safety classifiers distinguish between unauthorized exploit development and lawful local inspection of user owned software for interoperability or privacy auditing. If frontier hosted APIs tighten automated blocks on reverse engineering prompts, more software analysis workflows are likely to shift toward open weight models running through local MCP clients and self hosted inference engines.