opentdb.trivia.questions
Fetch random trivia questions from the Open Trivia Database. Returns up to 50 questions per call with category, difficulty, correct answer, incorrect answers, and a shuffled all_answers list for quiz presentation. HTML entities are decoded automatically. Filter by category (use opentdb.trivia.cat...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/opentdb.trivia.questions.md
What opentdb.trivia.questions does on Apibase
AI agents call opentdb.trivia.questions 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 |
|---|---|---|---|
type | string | — | Question type: multiple (4 choices) or boolean (True/False). Omit for both types. |
amount | integer | — | Number of trivia questions to return (default 10, max 50). |
category | integer | — | Category ID to filter by (e.g. 9=General Knowledge, 17=Science & Nature, 21=Sports, 23=History). Use opentdb.trivia.categories to list all 24 IDs. |
difficulty | string | — | Difficulty filter: easy, medium, or hard. Omit for mixed difficulty. |
Parameters from the server's own tool schema.
Why opentdb.trivia.questions is rated Low
Tool retrieves trivia data with no side effects, state changes, or operational impact.
From the tool's definition Fetch random trivia questions; Returns up to 50 questions; Filter by category, difficulty, type
Attacks that exploit this kind of access
The rule that runs opentdb.trivia.questions 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.questions, this is the rule to start with:
opentdb.trivia.questions 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.questions call is checked against it from then on.
Questions about opentdb.trivia.questions
Fetch random trivia questions from the Open Trivia Database. Returns up to 50 questions per call with category, difficulty, correct answer, incorrect answers, and a shuffled all_answers list for quiz presentation. HTML entities are decoded automatically. Filter by category (use opentdb.trivia.categories to get IDs), difficulty (easy/medium/hard), and type (multiple-choice or True/False). Examples: 10 general knowledge questions (no params), 5 hard science questions (category=17, amount=5, difficulty=hard), True/False history questions (category=23, type=boolean). Source: opentdb.com — CC BY-SA 4.0, user-contributed, 5000+ verified questions, 24 categories, free unlimited. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
opentdb.trivia.questions accepts 4 parameters: type, amount, category, difficulty. 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.questions: 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.questions 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.questions 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.questions. 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.questions 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