so_decompile
⭐反编译函数生成伪代码。支持radare2(默认,轻量)/ghidra(高质量)/simple(无依赖)
This record as markdown: /tools/1600822305-so-analyzer-mcp/so-decompile.md
What so_decompile does on SO Analyzer MCP
AI agents invoke so_decompile to trigger actions in SO Analyzer MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why so_decompile is rated High
This tool executes a decompilation engine (radare2, Ghidra, or a built-in disassembler) against a binary to produce pseudocode. It triggers external program execution whose effects depend on the input binary and chosen backend. While primarily a read/analysis operation, running decompilation tools like Ghidra or radare2 constitutes executing external processes, elevating it to Execute.
From the tool's definition 反编译函数生成伪代码 (decompile functions to generate pseudocode); supports radare2/ghidra/simple backends
Attacks that exploit this kind of access
The rule that runs so_decompile safely
PolicyLayer is an MCP gateway: it sits between your AI agents and SO Analyzer MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For so_decompile, this is the rule to start with:
so_decompile stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect SO Analyzer MCP, apply this rule, and every so_decompile call is checked against it from then on.
Questions about so_decompile
⭐反编译函数生成伪代码。支持radare2(默认,轻量)/ghidra(高质量)/simple(无依赖). It is categorised as a Execute tool in the SO Analyzer MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the SO Analyzer MCP server in PolicyLayer and add a rule for so_decompile: 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 SO Analyzer MCP. Nothing to install.
so_decompile is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the so_decompile 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 so_decompile. 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.
so_decompile is provided by the SO Analyzer MCP server (1600822305/so-analyzer-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on SO Analyzer, and thousands of servers like it.
Across the catalogue