canvas_trace_click_handler

Trace a click event from DOM to JS call stack.

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/canvas-trace-click-handler.md

WHAT IT DOES

What canvas_trace_click_handler does on Jshookmcp

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

Triggers browser DOM click events and traces JavaScript execution, constituting active browser interaction.

From the tool's definition Trace a click event from DOM to JS call stack

Attacks that exploit this kind of access

RECOMMENDED RULE

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

canvas_trace_click_handler Rate-limited

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

FAQ

Questions about canvas_trace_click_handler

What does the canvas_trace_click_handler tool do? +

Trace a click event from DOM to JS call stack. 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 canvas_trace_click_handler? +

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

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

Can I rate-limit canvas_trace_click_handler? +

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

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

canvas_trace_click_handler 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

browser_click on Percepta MCP Server →qt_click on Qt → All high-risk MCP tools → The MCP Attack Database →

Guides

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