search_posts

Search Gelbooru posts by tags, page, limit, or ID.

SERVERGelbooru MCP SOURCEcitronlegacy/gelbooru-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/citronlegacy-gelbooru-mcp/search-posts.md

WHAT IT DOES

What search_posts does on Gelbooru MCP

AI agents call search_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.

RISK

Why search_posts is rated Low

This tool performs a read-only retrieval operation against the Gelbooru API. It searches and retrieves posts based on specified parameters but does not create, modify, or delete any data. The operation is non-destructive and has no irreversible effects. Severity is low because misuse by an AI agent would only result in retrieving data that is already publicly available on the Gelbooru platform.

From the tool's definition Tool description states 'Search Gelbooru posts by tags, page, limit, or ID' — a query operation with no side effects. Returns search results without modifying, creating, or deleting data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs search_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 search_posts, this is the rule to start with:

search_posts Allowed

search_posts is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_posts": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Gelbooru MCP, apply this rule, and every search_posts call is checked against it from then on.

FAQ

Questions about search_posts

What does the search_posts tool do? +

Search Gelbooru posts by tags, page, limit, or ID. It is categorised as a Read tool in the Gelbooru MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_posts? +

Register the Gelbooru MCP server in PolicyLayer and add a rule for search_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.

What risk level is search_posts? +

search_posts is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit search_posts? +

Yes. Add a rate_limit block to the search_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.

How do I block search_posts completely? +

Set action: deny in the PolicyLayer policy for search_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.

What MCP server provides search_posts? +

search_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.

KEEP EXPLORING

More on Gelbooru, and thousands of servers like it.

This server

All 7 Gelbooru tools →

Across the catalogue

evaluate_search_quality on ACE-MCP →search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →