nemu_jni_handles
List all JNI object handles allocated in a session, with their kind and summary. Handles are opaque IDs (jclass, jstring, jbyteArray, jobject) that native code passes around. Use to verify mock setups and debug handle leaks. Optionally filter by kind (e.g.
This record as markdown: /tools/io-github-vmoranv-jshookmcp/nemu-jni-handles.md
What nemu_jni_handles does on Jshookmcp
AI agents call nemu_jni_handles to retrieve information from Jshookmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why nemu_jni_handles is rated Low
Tool queries and lists JNI handle allocations without modifying or executing code.
From the tool's definition List all JNI object handles allocated, debug handle leaks, filter by kind
Attacks that exploit this kind of access
The rule that runs nemu_jni_handles safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Jshookmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For nemu_jni_handles, this is the rule to start with:
nemu_jni_handles 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 Jshookmcp, apply this rule, and every nemu_jni_handles call is checked against it from then on.
Questions about nemu_jni_handles
List all JNI object handles allocated in a session, with their kind and summary. Handles are opaque IDs (jclass, jstring, jbyteArray, jobject) that native code passes around. Use to verify mock setups and debug handle leaks. Optionally filter by kind (e.g. It is categorised as a Read tool in the Jshookmcp MCP Server, which means it retrieves data without modifying state.
Register the Jshook MCP server in PolicyLayer and add a rule for nemu_jni_handles: 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 Jshookmcp. Nothing to install.
nemu_jni_handles 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 nemu_jni_handles 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 nemu_jni_handles. 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.
nemu_jni_handles is provided by the Jshook MCP server (@jshookmcp/jshook). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Jshook, and thousands of servers like it.
This server
Across the catalogue