webgpu_shader_disassemble
Parse WGSL or SPIR-V shader into AST and generate human-readable disassembly. Used for reverse engineering shader logic. SPIR-V input (hex/base64) is reflected into entry points, bindings, structs, and locations without compilation.
This record as markdown: /tools/io-github-vmoranv-jshookmcp/webgpu-shader-disassemble.md
What webgpu_shader_disassemble does on Jshookmcp
AI agents call webgpu_shader_disassemble 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 webgpu_shader_disassemble is rated Low
This tool performs static analysis and introspection of shader code—parsing and disassembly operations that retrieve and display information about shader structure without executing the shaders, modifying them, or triggering side effects. The purpose is reverse engineering and analysis, which is fundamentally a read operation.
From the tool's definition Tool description states it "Parse[s] WGSL or SPIR-V shader into AST and generate[s] human-readable disassembly" for "reverse engineering shader logic" with "reflection" of metadata. No modification, deletion, execution, or financial operations are described.
Attacks that exploit this kind of access
The rule that runs webgpu_shader_disassemble 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_shader_disassemble, this is the rule to start with:
webgpu_shader_disassemble is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Jshookmcp, apply this rule, and every webgpu_shader_disassemble call is checked against it from then on.
Questions about webgpu_shader_disassemble
Parse WGSL or SPIR-V shader into AST and generate human-readable disassembly. Used for reverse engineering shader logic. SPIR-V input (hex/base64) is reflected into entry points, bindings, structs, and locations without compilation. It is categorised as a Read tool in the Jshookmcp MCP Server, which means it retrieves data without modifying state.
Register the Jshook MCP server in PolicyLayer and add a rule for webgpu_shader_disassemble: 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.
webgpu_shader_disassemble 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 webgpu_shader_disassemble 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 webgpu_shader_disassemble. 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.
webgpu_shader_disassemble 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.
This server
Across the catalogue