AI agents call list_console_messages to retrieve information from Electron without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists console messages from an Electron app without creating, modifying, deleting, or executing any operations. It is a passive read operation with no side effects, making it a Read category risk with low severity.
From the tool's definition Tool name 'list_console_messages' and description indicate it 'List console messages' with retrieval and filtering capabilities by targetType. No modification, deletion, or execution of commands—purely querying existing console output.
Attacks that exploit this kind of access
List console messages. One line per message: msgid=N [main|renderer] [level] text. Use msgid in get_console_message. Filter by targetType (main|renderer|all). It is categorised as a Read tool in the Electron MCP Server, which means it retrieves data without modifying state.
Register the Electron MCP server in PolicyLayer and add a rule for list_console_messages: 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 Electron. Nothing to install.
list_console_messages is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_console_messages 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.
Set action: deny in the PolicyLayer policy for list_console_messages. 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.
list_console_messages is provided by the Electron MCP server (ohah/electron-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →