Skip to main content
Glama
@yawlabs/electron-mcp

@yawlabs/electron-mcp

Official
by YawLabs

electron_audit_ipc_security

Read-onlyIdempotent

Analyzes preload and main process IPC code to detect security issues like raw ipcRenderer exposure, missing sender validation, sync IPC, listener leaks, and prototype pollution.

Instructions

Analyze preload script and main process IPC code for security issues. Checks for: raw ipcRenderer exposure, missing sender validation, synchronous IPC usage, listener memory leaks, prototype pollution via contextBridge, and insecure channel patterns. Provide the actual code content to analyze.

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": "electron_audit_ipc_security"
  }
}

Input Schema

NameRequiredDescriptionDefault
mainCodeNoContent of the main process IPC handler code to analyze
preloadCodeNoContent of the preload script (preload.ts/js) to analyze
rendererCodeNoContent of renderer code that uses IPC, to check for anti-patterns

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.7.2
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.2.13

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value by disclosing the exact vulnerability categories it looks for, but says nothing about the result shape (severity levels, line references, pass/fail), whether the supplied code is stored or transmitted, or how large inputs are handled—topics the annotations do not cover.

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?

Two tight sentences: purpose first, then the check inventory, then the input requirement—well front-loaded with no filler. The check list is dense but each item earns its place by telling the agent what the tool detects.

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?

The tool is a read-only analyzer with no output schema, and every parameter is optional (required: 0), yet the description never explains what happens with partial input or what the report looks like. Adding a sentence on the minimum viable input and the shape of the findings would remove the remaining ambiguity.

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 100% and each of the three parameters already carries a clear per-field description, so the baseline of 3 applies. The description only gestures collectively at 'the actual code content' without clarifying how mainCode, preloadCode and rendererCode interact or which checks depend on which input.

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?

States a specific verb and resource ('Analyze preload script and main process IPC code') and enumerates the exact check classes (raw ipcRenderer exposure, sender validation, sync IPC, listener leaks, prototype pollution, channel patterns), which makes the scope clearly IPC-specific. It never names the broader electron_audit_security or electron_lint_security sibling, so the agent must infer the boundary itself.

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

Usage Guidelines2/5

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

The only guidance is the imperative 'Provide the actual code content to analyze,' which is an input instruction rather than a when-to-use rule. There is no statement of prerequisites, no indication of when to prefer this over a general security audit, and no guidance on what to do when only one of the three code inputs is available.

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