Find JNI methods in Android native libraries. Locates JNI_OnLoad, RegisterNatives calls, and Java_* exported functions.
AI agents call analyze_jni_methods to retrieve information from Kawaiidra MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs static binary analysis to identify JNI method signatures and entry points in Android native libraries. It retrieves information about code structure without executing code, modifying binaries, or triggering side effects. This is a pure reconnaissance/analysis operation typical of reverse engineering tools that examine code without altering it.
From the tool's definition Tool description states it 'Locates JNI_OnLoad, RegisterNatives calls, and Java_* exported functions' - all search/discovery operations with no modification or execution capability. The verb 'Find' and 'Locates' indicate read-only analysis.
Documented attack patterns abuse exactly the kind of access analyze_jni_methods gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Kawaiidra MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for analyze_jni_methods:
{
"version": "1",
"default": "deny",
"tools": {
"analyze_jni_methods": {}
}
} analyze_jni_methods is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Find JNI methods in Android native libraries. Locates JNI_OnLoad, RegisterNatives calls, and Java_* exported functions. It is categorised as a Read tool in the Kawaiidra MCP MCP Server, which means it retrieves data without modifying state.
Register the Kawaiidra MCP server in PolicyLayer and add a rule for analyze_jni_methods: 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 Kawaiidra MCP. Nothing to install.
analyze_jni_methods 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 analyze_jni_methods 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 analyze_jni_methods. 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.
analyze_jni_methods is provided by the Kawaiidra MCP server (wagonbomb/kawaiidra-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Kawaiidra MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
94 Kawaiidra MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.