Skip to main content
Glama
@yawlabs/electron-mcp

@yawlabs/electron-mcp

Official
by YawLabs

electron_lint_security

Read-onlyIdempotent

Analyzes Electron main, preload, and renderer code for dangerous security patterns such as shell.openExternal misuse, disabled webSecurity, and @electron/remote to flag OWASP-style risks before release.

Instructions

Static analysis of Electron code for dangerous patterns: shell.openExternal with user input, @electron/remote usage, disabled webSecurity, missing navigation restrictions, unrestricted window creation, and other OWASP-style vulnerabilities specific to Electron.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "code": "<code>"
    },
    "name": "electron_lint_security"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesSource code to analyze (main process, preload, or renderer)
fileTypeNoWhich process this code runs in. Helps scope the analysis. Defaults to 'main'.

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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered by structured data. The description adds the concrete vulnerability classes that are detected, which is useful, but says nothing about result format, severity levels, or false-positive behavior beyond those annotations.

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

Conciseness5/5

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

A single front-loaded sentence with no padding; every clause names a distinct vulnerability pattern, so nothing could be removed without losing detection scope.

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?

With no output schema, the description carries the burden of describing what a caller gets back, and it does not — no findings shape, severity ranking, or empty-result behavior. For a lint/analysis tool where the return value is the whole point, this is a meaningful gap even though inputs are fully documented.

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

Parameters4/5

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

Schema coverage is 100% and both parameters carry their own descriptions, so the schema does the heavy lifting and a baseline 3 applies. The description does add marginal meaning by naming 'user input' as the dangerous taint source, which hints at why code context matters, though it never explains how fileType changes analysis.

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 opens with a specific verb and resource ('Static analysis of Electron code') and enumerates concrete detection targets: shell.openExternal with user input, @electron/remote, disabled webSecurity, navigation restrictions, window creation. That is far more specific than the title, but it never distinguishes this from the broader electron_audit_security sibling, leaving overlap ambiguous.

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 it should pass a code snippet for security review, and the fileType enum hints at scoping. There is no explicit 'use this when...' statement, no exclusion relative to electron_audit_security or electron_check_deprecated_apis, and no mention that it analyzes supplied text rather than a project on disk.

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