process_windows

Get all window handles for a process.

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/process-windows.md

WHAT IT DOES

What process_windows does on Jshookmcp

AI agents call process_windows 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.

RISK

Why process_windows is rated Low

Retrieves window metadata without modifying state or executing code.

From the tool's definition Get all window handles for a process.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs process_windows safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Jshookmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For process_windows, this is the rule to start with:

process_windows Allowed

process_windows is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "process_windows": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Jshookmcp, apply this rule, and every process_windows call is checked against it from then on.

FAQ

Questions about process_windows

What does the process_windows tool do? +

Get all window handles for a process. 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 process_windows? +

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

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

Can I rate-limit process_windows? +

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

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

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

KEEP EXPLORING

More on Jshook, and thousands of servers like it.

This server

All 736 Jshook tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →