nemu_setup_java_mock
Register a mock Java method for JNI callbacks. returnInt/returnString/returnBytes for single constant; returnMap (JSON) for per-key dispatch: first Java arg matched as key→{type,value}. Single-constant is fallback for unmatched keys.
This record as markdown: /tools/io-github-vmoranv-jshookmcp/nemu-setup-java-mock.md
What nemu_setup_java_mock does on Jshookmcp
AI agents use nemu_setup_java_mock to create or update resources in Jshookmcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Jshookmcp environment.
Why nemu_setup_java_mock is rated Medium
Creates mock Java method registrations, modifying runtime behavior reversibly.
From the tool's definition Register a mock Java method for JNI callbacks
Attacks that exploit this kind of access
The rule that runs nemu_setup_java_mock 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_setup_java_mock, this is the rule to start with:
nemu_setup_java_mock stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_setup_java_mock call is checked against it from then on.
Questions about nemu_setup_java_mock
Register a mock Java method for JNI callbacks. returnInt/returnString/returnBytes for single constant; returnMap (JSON) for per-key dispatch: first Java arg matched as key→{type,value}. Single-constant is fallback for unmatched keys. It is categorised as a Write tool in the Jshookmcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Jshook MCP server in PolicyLayer and add a rule for nemu_setup_java_mock: 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_setup_java_mock is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the nemu_setup_java_mock 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_setup_java_mock. 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_setup_java_mock 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