Skip to main content
Glama
Electron Debug MCP Server

Electron Debug MCP Server

by amafjarkasi

ipc_fuzz_and_verify

Fuzz renderer-to-main IPC channels with boundary and malformed payloads, then verify crash resistance to identify process stability issues.

Instructions

Fuzz test renderer-to-main IPC channels with boundary and malformed payloads (null, prototype pollution, path traversal, oversized buffers) and verify process crash resistance.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ipc_fuzz_and_verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelsNoExplicit IPC channels to test. If omitted, automatically discovers active channels.
targetIdNo
processIdNoProcess ID. If omitted, uses the single running app.
timeoutMsNoTimeout per probe in ms (default 2000)
iterationsNoNumber of payload variations per channel (default 6)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.1

TDQS

B3.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description adds real behavioral detail beyond the annotations by enumerating payload categories (null, prototype pollution, path traversal, oversized buffers) and stating the tool checks crash resistance. However, it omits the consequence an agent most needs to know: that malformed/oversized payloads may actually crash or destabilize the target process, and whether the app must be restarted afterward. This sits in tension with destructiveHint=false, though it is not a direct contradiction since the tool only probes rather than mutating data.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence that front-loads the action and the payload categories, with no filler. It is arguably over-packed, but nothing is wasted and the key concept appears first.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter, open-world fuzzing tool with no output schema, the definition covers what it does and what it sends but not what it returns (crash found/not found, per-channel results) or the environmental/side-effect risks. An agent has enough to call it, but not enough to interpret or safely handle the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 80%, so the schema already documents channels, processId, timeoutMs, and iterations with defaults and bounds. The description adds nothing about parameters, which is acceptable given the baseline, but it also doesn't clarify how channels interact with auto-discovery or what targetId means.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb phrase ('Fuzz test renderer-to-main IPC channels ... and verify process crash resistance') and names the resource precisely, including the Electron renderer-to-main direction. It implicitly separates itself from siblings like ipc_invoke or ipc_tap by emphasizing fuzzing and crash verification, but never references an alternative explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: an agent can infer this is a security/robustness test of IPC channels, but the description never states when to choose this tool over ipc_invoke, ipc_tap, or ipc_schema_inference, nor does it give prerequisites (running app, attached target) or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools