wasm_vmp_trace

Read captured WASM VMP import-call traces from the current page.

SERVERJshookmcp SOURCE@jshookmcp/jshook

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-vmoranv-jshookmcp/wasm-vmp-trace.md

WHAT IT DOES

What wasm_vmp_trace does on Jshookmcp

AI agents call wasm_vmp_trace 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.

RISK

Why wasm_vmp_trace is rated Low

Tool retrieves existing trace data with no modification, deletion, or execution capability.

From the tool's definition Read captured WASM VMP import-call traces from current page

Attacks that exploit this kind of access

RECOMMENDED RULE

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

wasm_vmp_trace Allowed

wasm_vmp_trace is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "wasm_vmp_trace": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about wasm_vmp_trace

What does the wasm_vmp_trace tool do? +

Read captured WASM VMP import-call traces from the current page. It is categorised as a Read tool in the Jshookmcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on wasm_vmp_trace? +

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

wasm_vmp_trace is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit wasm_vmp_trace? +

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

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

wasm_vmp_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 →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →