# deleteCategory

Delete a category

Agent View of the PolicyLayer registry record for `deleteCategory`. HTML page: https://policylayer.com/tools/108yen-memo-mcp/deletecategory

## Facts

- Tool: `deleteCategory`
- Server: Memo (`108yen/memo-mcp`) — https://policylayer.com/tools/108yen-memo-mcp.md
- Homepage: https://github.com/108yen/memo-mcp
- Risk category: Destructive (Critical risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Hidden

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

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

## Why deleteCategory is rated Critical

This tool permanently removes a category from the memo database. Deletion is irreversible and cannot be undone without manual intervention or backups. The impact is high because deleting a category may cascade effects on associated memos or application logic that depends on that category.

From the tool's own definition: "Tool name is 'deleteCategory' and description states 'Delete a category'. The verb 'delete' combined with action on a stored category indicates irreversible removal of data."

## Use case

AI agents call deleteCategory to permanently remove resources in Memo, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "deleteCategory"
  ]
}
```

## Other tools on Memo (10)

- `deleteMemo` — Destructive — https://policylayer.com/tools/108yen-memo-mcp/deletememo.md
- `getCategories` — Read — https://policylayer.com/tools/108yen-memo-mcp/getcategories.md
- `getCategory` — Read — https://policylayer.com/tools/108yen-memo-mcp/getcategory.md
- `getMemo` — Read — https://policylayer.com/tools/108yen-memo-mcp/getmemo.md
- `getMemos` — Read — https://policylayer.com/tools/108yen-memo-mcp/getmemos.md
- `searchMemos` — Read — https://policylayer.com/tools/108yen-memo-mcp/searchmemos.md
- `createCategory` — Write — https://policylayer.com/tools/108yen-memo-mcp/createcategory.md
- `createMemo` — Write — https://policylayer.com/tools/108yen-memo-mcp/creatememo.md
- `updateCategory` — Write — https://policylayer.com/tools/108yen-memo-mcp/updatecategory.md
- `updateMemo` — Write — https://policylayer.com/tools/108yen-memo-mcp/updatememo.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=108yen-memo-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/108yen-memo-mcp