knowledge.wikidata.entity
Get structured data for a Wikidata entity by ID (e.g. Q42 = Douglas Adams). Returns labels, descriptions, aliases, and up to 20 property statements. 300+ languages supported. CC-0 (Wikidata)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/knowledge.wikidata.entity.md
What knowledge.wikidata.entity does on Apibase
AI agents call knowledge.wikidata.entity 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 |
|---|---|---|---|
id | string | Yes | Wikidata entity ID (e.g. "Q42" for Douglas Adams, "Q478214" for Tesla Inc). Get IDs from wikidata.search |
Parameters from the server's own tool schema.
Why knowledge.wikidata.entity is rated Low
Retrieves public Wikidata facts with no side effects, state changes, or execution capabilities.
From the tool's definition Get structured data for a Wikidata entity by ID. Returns labels, descriptions, aliases, property statements.
Attacks that exploit this kind of access
The rule that runs knowledge.wikidata.entity 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 knowledge.wikidata.entity, this is the rule to start with:
knowledge.wikidata.entity 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 knowledge.wikidata.entity call is checked against it from then on.
Questions about knowledge.wikidata.entity
Get structured data for a Wikidata entity by ID (e.g. Q42 = Douglas Adams). Returns labels, descriptions, aliases, and up to 20 property statements. 300+ languages supported. CC-0 (Wikidata). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
knowledge.wikidata.entity accepts 1 parameter: id. Required: 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 knowledge.wikidata.entity: 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.
knowledge.wikidata.entity 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 knowledge.wikidata.entity 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 knowledge.wikidata.entity. 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.
knowledge.wikidata.entity 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