# get_character_tags

Given a character name (e.g.

Agent View of the PolicyLayer registry record for `get_character_tags`. HTML page: https://policylayer.com/tools/citronlegacy-gelbooru-mcp/get-character-tags

## Facts

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

## Why get_character_tags is rated Low

This tool retrieves tag information associated with a character name from a public API. It has no side effects, cannot modify data, execute code, delete content, or involve financial transactions. The read-only nature and informational purpose classify it as a Read operation with low severity—misuse poses minimal risk beyond potential API rate limiting or returning unwanted search results.

From the tool's own definition: "Tool name 'get_character_tags' and server description indicate data retrieval: 'search posts, look up tags' and 'retrieve...all directly from your AI assistant.' The tool queries character tag information from the Gelbooru API without modifying, deleting, or…"

## Use case

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

## Other tools on Gelbooru MCP (6)

- `build_prompt` — Read — https://policylayer.com/tools/citronlegacy-gelbooru-mcp/build-prompt.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
- `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