Low Risk

get_wiki_info

[REAL-TIME API] Search Danbooru Wiki for tag/character information in real-time. Use this when: - You need information about what a tag means - You want to understand tag relationships or aliases - You need character background or copyright info

Part of the Danbooru Tags server.

get_wiki_info is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE DANBOORU TAGS →

Free to start. No card required.

AI agents call get_wiki_info to retrieve information from Danbooru Tags without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though get_wiki_info only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_wiki_info": {}
  }
}

See the full Danbooru Tags policy for all 4 tools.

Get this rule live on your own Danbooru Tags server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY DANBOORU TAGS →

These attack patterns abuse exactly the kind of access get_wiki_info gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so get_wiki_info only ever does what you allow.

SECURE DANBOORU TAGS →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the get_wiki_info tool do? +

[REAL-TIME API] Search Danbooru Wiki for tag/character information in real-time. Use this when: - You need information about what a tag means - You want to understand tag relationships or aliases - You need character background or copyright info. It is categorised as a Read tool in the Danbooru Tags MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_wiki_info? +

Register the Danbooru Tags MCP server in PolicyLayer and add a rule for get_wiki_info: 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 Danbooru Tags. Nothing to install.

What risk level is get_wiki_info? +

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

Can I rate-limit get_wiki_info? +

Yes. Add a rate_limit block to the get_wiki_info 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 get_wiki_info completely? +

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

get_wiki_info is provided by the Danbooru Tags MCP server (gamzadongza/danbooru-tags-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Danbooru Tags tool call.

Deterministic rules across all 4 Danbooru Tags tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.