query-hats-by-wearer

Find all hats currently worn by a specific address, grouped by tree with metadata

SERVERHats Protocol MCP Server SOURCEdennisonbertram/mcp-hats

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dennisonbertram-mcp-hats/query-hats-by-wearer.md

WHAT IT DOES

What query-hats-by-wearer does on Hats Protocol MCP Server

AI agents call query-hats-by-wearer to retrieve information from Hats Protocol MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why query-hats-by-wearer is rated Low

This tool queries blockchain data to retrieve information about which roles/permissions (hats) an address currently holds. It performs no writes, deletions, financial transactions, or code execution. The operation is purely informational and read-only.

From the tool's definition Tool description states 'Find all hats currently worn by a specific address, grouped by tree with metadata' - a retrieval operation with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs query-hats-by-wearer safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Hats Protocol MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For query-hats-by-wearer, this is the rule to start with:

query-hats-by-wearer Allowed

query-hats-by-wearer is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "query-hats-by-wearer": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Hats Protocol MCP Server, apply this rule, and every query-hats-by-wearer call is checked against it from then on.

FAQ

Questions about query-hats-by-wearer

What does the query-hats-by-wearer tool do? +

Find all hats currently worn by a specific address, grouped by tree with metadata. It is categorised as a Read tool in the Hats Protocol MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on query-hats-by-wearer? +

Register the Hats Protocol MCP Server MCP server in PolicyLayer and add a rule for query-hats-by-wearer: 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 Hats Protocol MCP Server. Nothing to install.

What risk level is query-hats-by-wearer? +

query-hats-by-wearer is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit query-hats-by-wearer? +

Yes. Add a rate_limit block to the query-hats-by-wearer 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.

How do I block query-hats-by-wearer completely? +

Set action: deny in the PolicyLayer policy for query-hats-by-wearer. 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.

What MCP server provides query-hats-by-wearer? +

query-hats-by-wearer is provided by the Hats Protocol MCP Server MCP server (dennisonbertram/mcp-hats). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Hats Protocol MCP Server, and thousands of servers like it.

This server

All 11 Hats Protocol MCP Server tools →

Across the catalogue

claude_query on Claude Bridge → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →