wasm_gallery_list_by_category
List WASM gallery templates filtered to a specific category. Use when native Glob is wrong because gallery templates are stored in the WASM runtime registry, not as individual filesystem files.
This record as markdown: /tools/io-github-ruvnet-claude-flow/wasm-gallery-list-by-category.md
What wasm_gallery_list_by_category does on Claude Flow
AI agents call wasm_gallery_list_by_category to retrieve information from Claude Flow without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why wasm_gallery_list_by_category is rated Low
This tool queries and returns filtered data from a WASM runtime registry without creating, modifying, deleting, or executing anything. It is a straightforward read operation with minimal security risk.
From the tool's definition Tool name contains 'list' and description explicitly states 'List WASM gallery templates filtered to a specific category' — a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs wasm_gallery_list_by_category safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Flow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wasm_gallery_list_by_category, this is the rule to start with:
wasm_gallery_list_by_category 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 Claude Flow, apply this rule, and every wasm_gallery_list_by_category call is checked against it from then on.
Questions about wasm_gallery_list_by_category
List WASM gallery templates filtered to a specific category. Use when native Glob is wrong because gallery templates are stored in the WASM runtime registry, not as individual filesystem files. It is categorised as a Read tool in the Claude Flow MCP Server, which means it retrieves data without modifying state.
Register the Claude Flow MCP server in PolicyLayer and add a rule for wasm_gallery_list_by_category: 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 Claude Flow. Nothing to install.
wasm_gallery_list_by_category 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 wasm_gallery_list_by_category 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 wasm_gallery_list_by_category. 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.
wasm_gallery_list_by_category is provided by the Claude Flow MCP server (claude-flow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Claude Flow, and thousands of servers like it.
This server
Across the catalogue