# search_users

Search Gelbooru users by name or name pattern.

Agent View of the PolicyLayer registry record for `search_users`. HTML page: https://policylayer.com/tools/citronlegacy-gelbooru-mcp/search-users

## Facts

- Tool: `search_users`
- 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": "search_users",
    "arguments": {}
  }
}
```

## Why search_users is rated Low

This tool retrieves user information from Gelbooru based on search criteria. It performs a query operation that returns data without creating, modifying, deleting, or executing any external operations. The action is read-only and poses minimal risk even if an AI agent misuses it—the worst case would be discovering user information that may already be public on the platform.

From the tool's own definition: "Tool description: 'Search Gelbooru users by name or name pattern.' The verb 'search' combined with read-only query of user information indicates data retrieval with no side effects."

## Use case

AI agents call search_users 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": {
    "search_users": {}
  }
}
```

## 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
- `get_deleted_posts` — Read — https://policylayer.com/tools/citronlegacy-gelbooru-mcp/get-deleted-posts.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

## 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