Show the current seek position and function name.
AI agents call Radare2_get_current_address 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.
This tool queries the current state of the reverse engineering analysis environment (seek position and function context) without modifying data, executing code, or triggering external operations. It is purely informational, analogous to a 'get' or 'query' operation. The blast radius of misuse is minimal—an agent could only retrieve analysis state information without harming systems or data.
From the tool's definition Tool name 'Radare2_get_current_address' and description 'Show the current seek position and function name' indicate retrieval of state information with no modification or execution.
Attacks that exploit this kind of access
Show the current seek position and function name. 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_get_current_address: 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_get_current_address 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_get_current_address 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_get_current_address. 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_get_current_address 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 →