start_trace_recording

Start recording debugger traces into a SQLite database for time-travel.

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/start-trace-recording.md

WHAT IT DOES

What start_trace_recording does on Jshookmcp

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

Initiates a debugger trace recording session, triggering external monitoring operations.

From the tool's definition Start recording debugger traces into a SQLite database

Attacks that exploit this kind of access

RECOMMENDED RULE

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

start_trace_recording Rate-limited

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

FAQ

Questions about start_trace_recording

What does the start_trace_recording tool do? +

Start recording debugger traces into a SQLite database for time-travel. 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 start_trace_recording? +

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

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

Can I rate-limit start_trace_recording? +

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

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

start_trace_recording 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

start_devtools_monitoring on Percepta MCP Server →team_manager_start_room on Team Manager MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

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