# get_deleted_posts

Retrieve deleted posts. Pass last_id to get everything deleted

Agent View of the PolicyLayer registry record for `get_deleted_posts`. HTML page: https://policylayer.com/tools/citronlegacy-gelbooru-mcp/get-deleted-posts

## Facts

- Tool: `get_deleted_posts`
- Server: Gelbooru MCP (`citronlegacy/gelbooru-mcp`) — https://policylayer.com/tools/citronlegacy-gelbooru-mcp.md
- Homepage: https://github.com/citronlegacy/gelbooru-mcp
- Risk category: Read (Low risk)
- Registry record: grade C, 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_deleted_posts",
    "arguments": {}
  }
}
```

## Why get_deleted_posts is rated Low

This tool retrieves or queries data about deleted posts without creating, modifying, deleting, executing code, or moving money. While the posts themselves are deleted, this tool only reads metadata about them—it has no side effects on the system. The blast radius of misuse is minimal; an agent retrieving deleted post information poses no significant security risk.

From the tool's own definition: "Tool name 'get_deleted_posts' and description 'Retrieve deleted posts' indicate a query/retrieval operation with no modification or deletion capability. The parameter 'last_id' suggests pagination for reading historical data."

Risk signals: Bulk/mass operation — affects multiple targets

## Use case

AI agents call get_deleted_posts to retrieve information from Gelbooru MCP 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 Gelbooru MCP:

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

## Other tools on Gelbooru MCP (6)

- `build_prompt` — Read — https://policylayer.com/tools/citronlegacy-gelbooru-mcp/build-prompt.md
- `get_character_tags` — Read — https://policylayer.com/tools/citronlegacy-gelbooru-mcp/get-character-tags.md
- `get_comments` — Read — https://policylayer.com/tools/citronlegacy-gelbooru-mcp/get-comments.md
- `search_posts` — Read — https://policylayer.com/tools/citronlegacy-gelbooru-mcp/search-posts.md
- `search_tags` — Read — https://policylayer.com/tools/citronlegacy-gelbooru-mcp/search-tags.md
- `search_users` — Read — https://policylayer.com/tools/citronlegacy-gelbooru-mcp/search-users.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=citronlegacy-gelbooru-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/citronlegacy-gelbooru-mcp