Ghidra on tsvinc

My guard read the tool's name, never its arguments

Mon, 26 Oct 2026 00:00:00 +0000

Builds on My guard blocked bash -c. Models write bash -lc., which explains the guard and what it hard-denies.

Every rename asked. Every comment asked. Every retyped variable stopped the agent and waited for me to click, and the binary it was all about never changed once. That was my guard's Ghidra policy doing exactly what I had written.

My agent-config templates give six terminal coding agents a Ghidra MCP server for reverse engineering, off by default and available on demand: pyghidra-mcp 0.2.7, GhidraMCP 2.0 or ReVa 7.3.1. The same guard that hard-denies destructive shell commands also decides about these tools, and its Ghidra policy was cautious: an allowlist of read verbs (get_, list_, decompile_ and a few more), a deny for deleting a binary, and a question for everything else.

The fix was in five agents. The sixth never called it.

Mon, 26 Oct 2026 00:00:00 +0000

Follows My guard read the tool's name, never its arguments, which introduced the fix this post tests.

The last post ended with a fix I was pleased with. My guard used to decide about Ghidra MCP tools by their name alone; now ghidraCheck(rules, tool, input, cwd) runs the guard's read rules over every path-like argument first, so an agent that asks Ghidra to import ~/.ssh/id_ed25519 into its project gets refused. Both guard implementations, TypeScript and Python, had cases for it. One agent, Claude Code, had been probed against a fake MCP server. The post said the pi and omp extensions, the OpenCode plugin and the Hermes and Claude Code hook "all go through it".

HTC Desire Z GPS: the Ghidra fix that landed 235 km away

Sun, 22 Feb 2026 00:00:00 +0000

For one night, this looked like the best result of the whole project. My HTC Desire Z, the 2010 Android slider that by then had its camera button wired to a waypoint logger, had spent hours by a window failing to find itself. Then I opened its 60 KB GPS library in Ghidra, found a switch that throws away "intermediate" positions, turned the switch on and rebooted. Two seconds after I pressed the camera button, a coordinate landed in the waypoint file. Six decimal places. Accuracy: zero metres.