opentdb.trivia.global_count
Get global question counts across the entire Open Trivia Database: total questions, verified (live and servable), pending (under review), and rejected, with a per-category breakdown. Useful for understanding database coverage — typically 5000+ verified questions spread across 24 categories. Note:...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/opentdb.trivia.global-count.md
What opentdb.trivia.global_count does on Apibase
AI agents call opentdb.trivia.global_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 |
|---|---|---|---|
_placeholder | string | — | No parameters required — returns global question counts and per-category breakdown. |
Parameters from the server's own tool schema.
Why opentdb.trivia.global_count is rated Low
Tool retrieves trivia database statistics without side effects or data modification capability.
From the tool's definition Get global question counts, database coverage, verified questions breakdown
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs opentdb.trivia.global_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.global_count, this is the rule to start with:
opentdb.trivia.global_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.global_count call is checked against it from then on.
Questions about opentdb.trivia.global_count
Get global question counts across the entire Open Trivia Database: total questions, verified (live and servable), pending (under review), and rejected, with a per-category breakdown. Useful for understanding database coverage — typically 5000+ verified questions spread across 24 categories. Note: only verified questions are returned by opentdb.trivia.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.global_count accepts 1 parameter: _placeholder. 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.global_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.global_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.global_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.global_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.global_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