Display binary headers and file information.
AI agents call Radare2_show_headers to retrieve information from Reversecore_MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Radare2_show_headers performs inspection and querying of binary structure metadata. It has no side effects, cannot alter binaries, and does not execute code or trigger external operations. This is purely a retrieval operation typical of reverse engineering analysis workflows.
From the tool's definition 'Display binary headers and file information' — this tool retrieves and presents metadata from binaries without modifying, executing, or deleting anything. Headers and file information are read-only artifacts of static analysis.
Attacks that exploit this kind of access
Display binary headers and file information. It is categorised as a Read tool in the Reversecore_MCP MCP Server, which means it retrieves data without modifying state.
Register the Reversecore_ MCP server in PolicyLayer and add a rule for Radare2_show_headers: 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 Reversecore_MCP. Nothing to install.
Radare2_show_headers 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 Radare2_show_headers 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 Radare2_show_headers. 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.
Radare2_show_headers is provided by the Reversecore_ MCP server (sjkim1127/reversecore_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →