AI agents call list_namespaces to retrieve information from GhidraMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns namespace information from a loaded Ghidra program. It performs a read-only operation that retrieves structural metadata about the program being analyzed. There are no modifications, deletions, code execution, or external side effects. The pagination parameter is a query control, not an action that modifies state.
From the tool's definition Tool name 'list_namespaces' and description 'List all non-global namespaces in the program with pagination' indicate a retrieval/enumeration operation with no side effects.
Attacks that exploit this kind of access
List all non-global namespaces in the program with pagination. It is categorised as a Read tool in the GhidraMCP MCP Server, which means it retrieves data without modifying state.
Register the Ghidra MCP server in PolicyLayer and add a rule for list_namespaces: 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 GhidraMCP. Nothing to install.
list_namespaces 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 list_namespaces 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 list_namespaces. 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.
list_namespaces is provided by the Ghidra MCP server (pr0cf5/ghidramcp). 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 →