# memory_hook_health

Hook 系统健康检查 — 查看最近 N 小时内哪些 hook 在触发、哪些静默失败。

Agent View of the PolicyLayer registry record for `memory_hook_health`. HTML page: https://policylayer.com/tools/soolaugust-0compactmem/memory-hook-health

## Facts

- Tool: `memory_hook_health`
- Server: 0CompactMem (`soolaugust/0compactmem`) — https://policylayer.com/tools/soolaugust-0compactmem.md
- Homepage: https://github.com/soolaugust/0CompactMem
- Risk category: Read (Low risk)
- Registry record: grade B, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "memory_hook_health",
    "arguments": {}
  }
}
```

## Why memory_hook_health is rated Low

This is a diagnostic/monitoring tool that inspects the state of memory hooks and their recent activity. It performs information retrieval only, with no side effects on the system. The blast radius if misused by an AI agent is minimal—an agent could potentially gather debugging information about system internals, but cannot modify or delete data, execute operations, or trigger financial impacts.

From the tool's own definition: "Tool name 'memory_hook_health' and description indicate it 'views' (查看) which hooks are triggering and silently failing within recent N hours."

## Use case

AI agents call memory_hook_health to retrieve information from 0CompactMem without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches 0CompactMem:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "memory_hook_health": {}
  }
}
```

## Other tools on 0CompactMem (7)

- `list_pinned` — Read — https://policylayer.com/tools/soolaugust-0compactmem/list-pinned.md
- `memory_applied` — Read — https://policylayer.com/tools/soolaugust-0compactmem/memory-applied.md
- `memory_lookup` — Read — https://policylayer.com/tools/soolaugust-0compactmem/memory-lookup.md
- `memory_stats` — Read — https://policylayer.com/tools/soolaugust-0compactmem/memory-stats.md
- `memory_write` — Write — https://policylayer.com/tools/soolaugust-0compactmem/memory-write.md
- `pin_memory` — Write — https://policylayer.com/tools/soolaugust-0compactmem/pin-memory.md
- `unpin_memory` — Write — https://policylayer.com/tools/soolaugust-0compactmem/unpin-memory.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=soolaugust-0compactmem · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/soolaugust-0compactmem