This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/mhw-weapons.md
What mhw_weapons does on UnClick
AI agents call mhw_weapons to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
type | string | — | Weapon type (e.g. great-sword, long-sword, bow, hammer). |
limit | number | — | Max results (default 10). |
Parameters from the server's own tool schema.
Why mhw_weapons is rated Low
This tool retrieves or lists weapon information from Monster Hunter World, allowing users to browse and filter by weapon type. It performs no side effects, does not execute code or commands, does not create or modify data, and does not delete or move resources. It is a straightforward read-only data retrieval tool with minimal security risk.
From the tool's definition Tool name 'mhw_weapons' and description 'Browse Monster Hunter World weapons by type' indicate a query/retrieval operation with no modification or execution capability.
Attacks that exploit this kind of access
The rule that runs mhw_weapons safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mhw_weapons, this is the rule to start with:
mhw_weapons 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 UnClick, apply this rule, and every mhw_weapons call is checked against it from then on.
Questions about mhw_weapons
Browse Monster Hunter World weapons by type. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
mhw_weapons accepts 2 parameters: type, limit. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for mhw_weapons: 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 UnClick. Nothing to install.
mhw_weapons 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 mhw_weapons 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 mhw_weapons. 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.
mhw_weapons is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue