crypto_test_harness
Run extracted crypto code in worker_threads + vm sandbox and return deterministic test results.
This record as markdown: /tools/io-github-vmoranv-jshookmcp/crypto-test-harness.md
What crypto_test_harness does on Jshookmcp
AI agents invoke crypto_test_harness 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.
Why crypto_test_harness is rated High
Executes arbitrary crypto code in a sandbox; misuse could run malicious code.
From the tool's definition Run extracted crypto code in worker_threads + vm sandbox
Attacks that exploit this kind of access
The rule that runs crypto_test_harness 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 crypto_test_harness, this is the rule to start with:
crypto_test_harness 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Jshookmcp, apply this rule, and every crypto_test_harness call is checked against it from then on.
Questions about crypto_test_harness
Run extracted crypto code in worker_threads + vm sandbox and return deterministic test results. 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.
Register the Jshook MCP server in PolicyLayer and add a rule for crypto_test_harness: 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.
crypto_test_harness is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the crypto_test_harness 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 crypto_test_harness. 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.
crypto_test_harness 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.
Across the catalogue