diagnose_setup

THE RISK

Low Risk

Why diagnose_setup needs a policy

The tool performs diagnostic checks, which is a read/inspection operation that queries the state of the Ghidra installation and environment. It does not modify, execute arbitrary code, delete data, or involve financial operations. Severity is low as it only reads system configuration state.

From the tool's definition Run diagnostic checks on Ghidra installation and environment

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

POLICY

How to control diagnose_setup

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

policy.json

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

diagnose_setup 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 Binary MCP Server — 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 Binary MCP Server tools

Destructive delete_session Delete a saved session. Destructive clean_cache clean_cache Execute batch_decompile batch_decompile Execute start_analysis_session start_analysis_session Write generate_yara_rule_from_session generate_yara_rule_from_session Write save_session save_session Read decompile_dotnet_assembly decompile_dotnet_assembly Read decompile_dotnet_type decompile_dotnet_type

All 59 Binary MCP Server 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 diagnose_setup

What does the diagnose_setup tool do? +

Run diagnostic checks on Ghidra installation and environment. It is categorised as a Read tool in the Binary MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on diagnose_setup? +

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

What risk level is diagnose_setup? +

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

Can I rate-limit diagnose_setup? +

Yes. Add a rate_limit block to the diagnose_setup 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 diagnose_setup completely? +

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

diagnose_setup is provided by the Binary MCP Server MCP server (sarks0/binary-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Binary MCP Server tool call.

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

CHECK YOUR STACK →