so_exports

What so_exports does on SO Analyzer MCP

AI agents call so_exports to retrieve information from SO Analyzer MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why so_exports is rated Low

Analyzing exported functions from binary libraries is a read-only operation that gathers information about compiled code structure. While it supports security analysis (potentially for identifying vulnerabilities), it does not execute code, modify binaries, delete data, or move money. The tool enables passive reconnaissance of native library internals, making it a Read category risk.

From the tool's definition so_exports retrieves a list of exported functions from SO files (native Android libraries). The description translates to 'get list of SO exported functions.' This is a query/inspection operation with no modification capability.

The rule that runs so_exports safely

PolicyLayer is an MCP gateway: it sits between your AI agents and SO Analyzer MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For so_exports, this is the rule to start with:

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

Questions about so_exports