This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/hp-by-house.md
What hp_by_house does on UnClick
AI agents call hp_by_house 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 |
|---|---|---|---|
house | string | Yes | House name: gryffindor, slytherin, hufflepuff, or ravenclaw |
Parameters from the server's own tool schema.
Why hp_by_house is rated Low
This is a straightforward read operation that queries and returns publicly available Harry Potter character information. It has no side effects, does not modify data, does not execute code, and poses no destructive or financial risk. The low severity reflects minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'hp_by_house' and description 'List characters by Hogwarts house' indicate a query/retrieval operation that returns Harry Potter character data filtered by house affiliation.
Attacks that exploit this kind of access
The rule that runs hp_by_house 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 hp_by_house, this is the rule to start with:
hp_by_house 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 hp_by_house call is checked against it from then on.
Questions about hp_by_house
List characters by Hogwarts house. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
hp_by_house accepts 1 parameter: house. Required: house. 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 hp_by_house: 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.
hp_by_house 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 hp_by_house 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 hp_by_house. 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.
hp_by_house 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