New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

electron_verify_integrity

Verify Electron ASAR integrity: parse the ElectronAsarIntegrity JSON embedded in the main binary, locate each referenced ASAR, and compare the on-disk SHA256/SHA512 hash against the embedded hash. A mismatch means the ASAR was tampered with after build.

SERVERJshookmcp SOURCE@jshookmcp/jshook
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-vmoranv-jshookmcp/electron-verify-integrity.md

What electron_verify_integrity does on Jshookmcp

AI agents call electron_verify_integrity to retrieve information from Jshookmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why electron_verify_integrity is rated Low

Tool only reads and verifies file integrity; performs no modifications or side effects.

From the tool's definition Verify, parse, compare hash, detect tampering—no modification.

Questions about electron_verify_integrity

What does the electron_verify_integrity tool do? +

Verify Electron ASAR integrity: parse the ElectronAsarIntegrity JSON embedded in the main binary, locate each referenced ASAR, and compare the on-disk SHA256/SHA512 hash against the embedded hash. A mismatch means the ASAR was tampered with after build. It is categorised as a Read tool in the Jshookmcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on electron_verify_integrity? +

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

electron_verify_integrity is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit electron_verify_integrity? +

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

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

electron_verify_integrity 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.

More on Jshook, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Jshook's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.