nemu_call_jni_export

Invoke an exported

SERVERJshookmcp SOURCE@jshookmcp/jshook

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-vmoranv-jshookmcp/nemu-call-jni-export.md

WHAT IT DOES

What nemu_call_jni_export does on Jshookmcp

AI agents invoke nemu_call_jni_export to trigger actions in Jshookmcp. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why nemu_call_jni_export is rated High

Invoking JNI exports runs native code; description is truncated and uninformative.

From the tool's definition Invoke an exported

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs nemu_call_jni_export 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_call_jni_export, this is the rule to start with:

nemu_call_jni_export Rate-limited

nemu_call_jni_export stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "nemu_call_jni_export": {
      "limits": [
        {
          "counter": "nemu_call_jni_export_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Jshookmcp, apply this rule, and every nemu_call_jni_export call is checked against it from then on.

FAQ

Questions about nemu_call_jni_export

What does the nemu_call_jni_export tool do? +

Invoke an exported. It is categorised as a Execute tool in the Jshookmcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on nemu_call_jni_export? +

Register the Jshook MCP server in PolicyLayer and add a rule for nemu_call_jni_export: 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.

What risk level is nemu_call_jni_export? +

nemu_call_jni_export is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit nemu_call_jni_export? +

Yes. Add a rate_limit block to the nemu_call_jni_export 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.

How do I block nemu_call_jni_export completely? +

Set action: deny in the PolicyLayer policy for nemu_call_jni_export. 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.

What MCP server provides nemu_call_jni_export? +

nemu_call_jni_export 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.

KEEP EXPLORING

More on Jshook, and thousands of servers like it.

This server

All 736 Jshook tools → High-risk tools on this server →

Across the catalogue

call_rpc on Frida Game Hacking MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →