check-hat-wearer
Check if an address is currently wearing a specific hat and in good standing
This record as markdown: /tools/dennisonbertram-mcp-hats/check-hat-wearer.md
What check-hat-wearer does on Hats Protocol MCP Server
AI agents call check-hat-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.
Why check-hat-wearer is rated Low
This tool performs a read-only verification of role status. It queries whether an address holds a specific hat (role) and its standing status, with no side effects, data modification, or blockchain state changes. This is purely informational retrieval, consistent with the Read category.
From the tool's definition Tool name 'check-hat-wearer' and description 'Check if an address is currently wearing a specific hat and in good standing' indicate a query operation that retrieves the status of a role/permission without modification.
Attacks that exploit this kind of access
The rule that runs check-hat-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 check-hat-wearer, this is the rule to start with:
check-hat-wearer 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 Hats Protocol MCP Server, apply this rule, and every check-hat-wearer call is checked against it from then on.
Questions about check-hat-wearer
Check if an address is currently wearing a specific hat and in good standing. It is categorised as a Read tool in the Hats Protocol MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Hats Protocol MCP Server MCP server in PolicyLayer and add a rule for check-hat-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.
check-hat-wearer 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 check-hat-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.
Set action: deny in the PolicyLayer policy for check-hat-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.
check-hat-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.
More on Hats Protocol MCP Server, and thousands of servers like it.
This server
Across the catalogue