opentdb.trivia.category_count
Get the number of verified trivia questions available in a specific category, broken down by difficulty (easy, medium, hard). Useful for checking availability before requesting questions with opentdb.trivia.questions — if you request more questions than exist in a filtered query, the API returns ...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/opentdb.trivia.category-count.md
What opentdb.trivia.category_count does on Apibase
AI agents call opentdb.trivia.category_count to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
category_id | integer | Yes | Category ID (9–32). Use opentdb.trivia.categories to list all IDs. Examples: 9=General Knowledge, 17=Science & Nature, 21=Sports, 23=History. |
Parameters from the server's own tool schema.
Why opentdb.trivia.category_count is rated Low
Retrieves metadata about trivia question availability with no side effects or data modification.
From the tool's definition Get the number of verified trivia questions available in a specific category
Attacks that exploit this kind of access
The rule that runs opentdb.trivia.category_count safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For opentdb.trivia.category_count, this is the rule to start with:
opentdb.trivia.category_count is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every opentdb.trivia.category_count call is checked against it from then on.
Questions about opentdb.trivia.category_count
Get the number of verified trivia questions available in a specific category, broken down by difficulty (easy, medium, hard). Useful for checking availability before requesting questions with opentdb.trivia.questions — if you request more questions than exist in a filtered query, the API returns empty results. Example: category 9 (General Knowledge) has ~469 verified questions. Source: opentdb.com — CC BY-SA 4.0, free unlimited. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
opentdb.trivia.category_count accepts 1 parameter: category_id. Required: category_id. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for opentdb.trivia.category_count: 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 Apibase. Nothing to install.
opentdb.trivia.category_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 opentdb.trivia.category_count 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.
Set action: deny in the PolicyLayer policy for opentdb.trivia.category_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.
opentdb.trivia.category_count is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue