get_deleted_posts
Retrieve deleted posts. Pass last_id to get everything deleted
This record as markdown: /tools/citronlegacy-gelbooru-mcp/get-deleted-posts.md
What get_deleted_posts does on Gelbooru MCP
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.
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 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 signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs get_deleted_posts safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gelbooru MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_deleted_posts, this is the rule to start with:
get_deleted_posts is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Gelbooru MCP, apply this rule, and every get_deleted_posts call is checked against it from then on.
Questions about get_deleted_posts
Retrieve deleted posts. Pass last_id to get everything deleted. It is categorised as a Read tool in the Gelbooru MCP MCP Server, which means it retrieves data without modifying state.
Register the Gelbooru MCP server in PolicyLayer and add a rule for get_deleted_posts: 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 Gelbooru MCP. Nothing to install.
get_deleted_posts is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_deleted_posts 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.
Set action: deny in the PolicyLayer policy for get_deleted_posts. 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.
get_deleted_posts is provided by the Gelbooru MCP server (citronlegacy/gelbooru-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gelbooru, and thousands of servers like it.
This server
Across the catalogue