# get_memory_stats

Get statistics about stored memories

Agent View of the PolicyLayer registry record for `get_memory_stats`. HTML page: https://policylayer.com/tools/0xrelogic-cognio/get-memory-stats

## Facts

- Tool: `get_memory_stats`
- Server: Cognio (`0xrelogic/cognio`) — https://policylayer.com/tools/0xrelogic-cognio.md
- Homepage: https://github.com/0xReLogic/Cognio
- Risk category: Read (Low risk)
- Registry record: grade D, 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": "get_memory_stats",
    "arguments": {}
  }
}
```

## Why get_memory_stats is rated Low

This tool retrieves statistical information about memories (e.g., count, storage usage, date ranges) rather than reading individual memory contents. It is read-only with no side effects. The blast radius of misuse is minimal—an AI agent obtaining memory statistics poses no risk of data loss, modification, or unauthorized access to sensitive memory contents themselves.

From the tool's own definition: "Tool name 'get_memory_stats' combined with description 'Get statistics about stored memories' indicates a query operation that retrieves aggregate data without modification."

## Use case

AI agents call get_memory_stats to retrieve information from Cognio 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 Cognio:

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

## Other tools on Cognio (11)

- `delete_memory` — Destructive — https://policylayer.com/tools/0xrelogic-cognio/delete-memory.md
- `export_memories` — Read — https://policylayer.com/tools/0xrelogic-cognio/export-memories.md
- `get_active_project` — Read — https://policylayer.com/tools/0xrelogic-cognio/get-active-project.md
- `get_memory` — Read — https://policylayer.com/tools/0xrelogic-cognio/get-memory.md
- `list_memories` — Read — https://policylayer.com/tools/0xrelogic-cognio/list-memories.md
- `list_projects` — Read — https://policylayer.com/tools/0xrelogic-cognio/list-projects.md
- `search_memory` — Read — https://policylayer.com/tools/0xrelogic-cognio/search-memory.md
- `summarize_text` — Read — https://policylayer.com/tools/0xrelogic-cognio/summarize-text.md
- `archive_memory` — Write — https://policylayer.com/tools/0xrelogic-cognio/archive-memory.md
- `save_memory` — Write — https://policylayer.com/tools/0xrelogic-cognio/save-memory.md
- `set_active_project` — Write — https://policylayer.com/tools/0xrelogic-cognio/set-active-project.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=0xrelogic-cognio · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/0xrelogic-cognio