wasm_gallery_add_custom
Add a custom agent template to the WASM gallery registry. Use when native Write is wrong because custom templates must be registered inside the WASM runtime store, not written as plain files.
This record as markdown: /tools/hamza-agent-hub-252/wasm-gallery-add-custom.md
What wasm_gallery_add_custom does on Hamza Agent Hub 252
AI agents use wasm_gallery_add_custom to create or update resources in Hamza Agent Hub 252, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hamza Agent Hub 252 environment.
Why wasm_gallery_add_custom is rated Medium
This tool creates or registers new agent templates in the WASM runtime store, which is a reversible modification operation. The act of adding a template can typically be undone by removal or modification. While it affects the agent runtime environment, it does not execute arbitrary code, delete irreversibly, or move financial resources.
From the tool's definition 'Add a custom agent template to the WASM gallery registry' — creates/registers new data (a custom agent template) in a registry system
Attacks that exploit this kind of access
The rule that runs wasm_gallery_add_custom safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hamza Agent Hub 252, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wasm_gallery_add_custom, this is the rule to start with:
wasm_gallery_add_custom stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Hamza Agent Hub 252, apply this rule, and every wasm_gallery_add_custom call is checked against it from then on.
Questions about wasm_gallery_add_custom
Add a custom agent template to the WASM gallery registry. Use when native Write is wrong because custom templates must be registered inside the WASM runtime store, not written as plain files. It is categorised as a Write tool in the Hamza Agent Hub 252 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Hamza Agent Hub 252 MCP server in PolicyLayer and add a rule for wasm_gallery_add_custom: 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 Hamza Agent Hub 252. Nothing to install.
wasm_gallery_add_custom is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the wasm_gallery_add_custom 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_add_custom. 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_add_custom is provided by the Hamza Agent Hub 252 MCP server (hamzachallenge3-dev/hamza-agent-hub-252). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hamza Agent Hub 252, and thousands of servers like it.
This server
Across the catalogue