**[REAL-TIME API]** Get the total number of posts for a specific tag. Use this when: - You want to know how many posts exist for a character/tag BEFORE collecting data - You need to estimate collection time and resources - You want to verify data completeness after collection Returns only the p...
Single-target operation
Part of the Danbooru Tags MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call get_post_count 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_post_count 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.
tools:
get_post_count:
rules:
- action: allowSee the full Danbooru Tags policy for all 4 tools.
Agents calling read-class tools like get_post_count have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
**[REAL-TIME API]** Get the total number of posts for a specific tag. Use this when: - You want to know how many posts exist for a character/tag BEFORE collecting data - You need to estimate collection time and resources - You want to verify data completeness after collection Returns only the post count. Use danbooru-turso-mcp.collect_and_save for actual data collection.. It is categorised as a Read tool in the Danbooru Tags MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for get_post_count. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Danbooru Tags MCP server.
get_post_count 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_post_count rule in your Intercept 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 Intercept policy for get_post_count. 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_post_count is provided by the Danbooru Tags MCP server (gamzadongza/danbooru-tags-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept