Low Risk

wear_hat

Activate an Intelligence Pack. Imports expert knowledge into your memory. Your own memories layer on top.

Part of the Memory Nexus server.

wear_hat is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE MEMORY NEXUS →

Free to start. No card required.

AI agents call wear_hat to retrieve information from Memory Nexus without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though wear_hat only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "wear_hat": {}
  }
}

See the full Memory Nexus policy for all 18 tools.

Get this rule live on your own Memory Nexus server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY MEMORY NEXUS →

View all 18 tools →

These attack patterns abuse exactly the kind of access wear_hat gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so wear_hat only ever does what you allow.

SECURE MEMORY NEXUS →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the wear_hat tool do? +

Activate an Intelligence Pack. Imports expert knowledge into your memory. Your own memories layer on top.. It is categorised as a Read tool in the Memory Nexus MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on wear_hat? +

Register the Memory Nexus MCP server in PolicyLayer and add a rule for wear_hat: 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 Memory Nexus. Nothing to install.

What risk level is wear_hat? +

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

Can I rate-limit wear_hat? +

Yes. Add a rate_limit block to the wear_hat 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 wear_hat completely? +

Set action: deny in the PolicyLayer policy for wear_hat. 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 wear_hat? +

wear_hat is provided by the Memory Nexus MCP server (@memory-nexus/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Memory Nexus tool call.

Deterministic rules across all 18 Memory Nexus tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.