iceandfire_houses
Search noble houses from A Song of Ice and Fire (Game of Thrones).
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/iceandfire-houses.md
What iceandfire_houses does on UnClick
AI agents call iceandfire_houses 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 |
|---|---|---|---|
name | string | — | House name to search for |
limit | number | — | Results per page (default 10) |
Parameters from the server's own tool schema.
Why iceandfire_houses is rated Low
This tool retrieves or queries data about fictional noble houses with no side effects, data modifications, code execution, financial impact, or destructive capabilities. It is a straightforward read-only search tool.
From the tool's definition Tool name 'iceandfire_houses' and description 'Search noble houses from A Song of Ice and Fire (Game of Thrones)' indicate a search/query operation over fictional Game of Thrones data.
Attacks that exploit this kind of access
The rule that runs iceandfire_houses 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 iceandfire_houses, this is the rule to start with:
iceandfire_houses 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 iceandfire_houses call is checked against it from then on.
Questions about iceandfire_houses
Search noble houses from A Song of Ice and Fire (Game of Thrones). It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
iceandfire_houses accepts 2 parameters: name, 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 iceandfire_houses: 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.
iceandfire_houses 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 iceandfire_houses 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 iceandfire_houses. 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.
iceandfire_houses 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