wasm_instrument_trace

Generate a JS instrumentation wrapper for a .wasm module.

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/wasm-instrument-trace.md

WHAT IT DOES

What wasm_instrument_trace does on Jshookmcp

AI agents invoke wasm_instrument_trace 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 wasm_instrument_trace is rated High

Generates executable JS instrumentation code wrapping a WebAssembly module, enabling arbitrary execution.

From the tool's definition Generate JS instrumentation wrapper for a .wasm module

Attacks that exploit this kind of access

RECOMMENDED RULE

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

wasm_instrument_trace Rate-limited

wasm_instrument_trace 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": {
    "wasm_instrument_trace": {
      "limits": [
        {
          "counter": "wasm_instrument_trace_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 wasm_instrument_trace call is checked against it from then on.

FAQ

Questions about wasm_instrument_trace

What does the wasm_instrument_trace tool do? +

Generate a JS instrumentation wrapper for a .wasm module. 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 wasm_instrument_trace? +

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

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

Can I rate-limit wasm_instrument_trace? +

Yes. Add a rate_limit block to the wasm_instrument_trace 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 wasm_instrument_trace completely? +

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

wasm_instrument_trace 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

All high-risk MCP tools → The MCP Attack Database →

Guides

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