analyze_funcs

THE RISK

Low Risk

Why analyze_funcs needs a policy

The tool performs read-only analysis of functions in a reverse engineering database — decompiling code, listing cross-references, callees, strings, constants, and basic blocks. No data is modified or executed. Medium severity because it exposes potentially sensitive binary/source code internals.

From the tool's definition Comprehensive function analysis: decompilation, xrefs, callees, strings, constants, blocks

Documented attack patterns abuse exactly the kind of access analyze_funcs gives an agent:

POLICY

How to control analyze_funcs

PolicyLayer is an MCP gateway — it sits between your AI agents and Ida Domain, and nothing reaches the server without passing your rules. This is the rule we recommend for analyze_funcs:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "analyze_funcs": {}
  }
}

analyze_funcs is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Ida Domain — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Ida Domain tools

Destructive dbg_delete_bp Delete breakpoints Destructive delete_stack Delete stack vars Destructive close_database Close the project's IDA database and terminate its worker process. Execute callgraph Build call graph starting from root functions Execute dbg_run_to Run to address Execute dbg_start Start debugger Execute py_eval Execute Python code in IDA context Execute dbg_continue Continue debugger

All 74 Ida Domain tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about analyze_funcs

What does the analyze_funcs tool do? +

Comprehensive function analysis: decompilation, xrefs, callees, strings, constants, blocks. It is categorised as a Read tool in the Ida Domain MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on analyze_funcs? +

Register the Ida Domain MCP server in PolicyLayer and add a rule for analyze_funcs: 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 Ida Domain. Nothing to install.

What risk level is analyze_funcs? +

analyze_funcs is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit analyze_funcs? +

Yes. Add a rate_limit block to the analyze_funcs 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.

How do I block analyze_funcs completely? +

Set action: deny in the PolicyLayer policy for analyze_funcs. 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.

What MCP server provides analyze_funcs? +

analyze_funcs is provided by the Ida Domain MCP server (xxyyue/ida_domain_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Ida Domain tool call.

Start from Ida Domain, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →