Find Ghidra APIs commonly used alongside a given class or method.
AI agents call list_related_apis to retrieve information from Ghidra Api without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries information from Ghidra's API documentation index to provide relationship data about APIs. It performs a lookup operation without modifying, executing, or deleting any data. The server's purpose is to help LLMs understand API call-flows, making this purely informational.
From the tool's definition The tool 'list_related_apis' is described as finding/querying 'Ghidra APIs commonly used alongside a given class or method.' The verb 'find' and the context of retrieving API information from an extracted index indicates data retrieval with no side effects.
Attacks that exploit this kind of access
Find Ghidra APIs commonly used alongside a given class or method. It is categorised as a Read tool in the Ghidra Api MCP Server, which means it retrieves data without modifying state.
Register the Ghidra Api MCP server in PolicyLayer and add a rule for list_related_apis: 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 Ghidra Api. Nothing to install.
list_related_apis 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_related_apis 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_related_apis. 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_related_apis is provided by the Ghidra Api MCP server (taardisaa/ghidra-api-mcp). 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 →