webgpu_adapter_info

Get WebGPU adapter information (vendor, architecture, device). Used for fingerprinting GPU capabilities and detecting hardware-level vulnerabilities.

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/webgpu-adapter-info.md

WHAT IT DOES

What webgpu_adapter_info does on Jshookmcp

AI agents call webgpu_adapter_info 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 webgpu_adapter_info is rated Low

This tool queries and retrieves GPU metadata without executing code, modifying data, or triggering external operations. The 'Get' verb and informational nature (vendor, architecture, device data) align with Read category.

From the tool's definition Tool description states 'Get WebGPU adapter information (vendor, architecture, device)' — a retrieval operation with no modification or execution.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs webgpu_adapter_info 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 webgpu_adapter_info, this is the rule to start with:

webgpu_adapter_info Allowed

webgpu_adapter_info 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": {
    "webgpu_adapter_info": {}
  }
}

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 webgpu_adapter_info call is checked against it from then on.

FAQ

Questions about webgpu_adapter_info

What does the webgpu_adapter_info tool do? +

Get WebGPU adapter information (vendor, architecture, device). Used for fingerprinting GPU capabilities and detecting hardware-level vulnerabilities. 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 webgpu_adapter_info? +

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

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

Can I rate-limit webgpu_adapter_info? +

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

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

webgpu_adapter_info 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 →