This record as markdown: /tools/1600822305-so-analyzer-mcp/so-imports.md
What so_imports does on SO Analyzer MCP
AI agents call so_imports 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_imports is rated Low
This tool retrieves metadata about imported functions in native Android SO libraries. It performs static analysis and introspection only—extracting information about symbols and function dependencies without executing code, modifying binaries, or causing side effects. It is a Read operation with low severity since the blast radius of misuse is limited to information disclosure.
From the tool's definition Tool name 'so_imports' and description '获取SO导入函数列表' (get SO imported function list) indicate a data retrieval operation that queries imported functions from a binary artifact without modifying it.
Attacks that exploit this kind of access
The rule that runs so_imports 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_imports, this is the rule to start with:
so_imports is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect SO Analyzer MCP, apply this rule, and every so_imports call is checked against it from then on.
Questions about so_imports
获取SO导入函数列表. It is categorised as a Read tool in the SO Analyzer MCP MCP Server, which means it retrieves data without modifying state.
Register the SO Analyzer MCP server in PolicyLayer and add a rule for so_imports: 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 SO Analyzer MCP. Nothing to install.
so_imports 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 so_imports 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 so_imports. 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.
so_imports is provided by the SO Analyzer MCP server (1600822305/so-analyzer-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on SO Analyzer, and thousands of servers like it.
This server
Across the catalogue