AI agents call wikidata.entity to retrieve information from Mcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns metadata and linked data from Wikidata (a public, CC0-licensed knowledge base). The operation is purely informational with no side effects, no code execution, and no ability to modify or delete data. The blast radius of misuse is minimal — at worst, an agent could retrieve unwanted information or exhaust rate limits, neither of which causes harm. It is a straightforward Read operation.
From the tool's definition Tool description states 'Fetch a Wikidata entity' — a retrieval operation that queries public, read-only structured data from Wikidata's knowledge graph. No modification, deletion, execution, or financial transaction occurs.
Attacks that exploit this kind of access
Fetch a Wikidata entity (Q42, P31, etc.) — structured knowledge-graph record with labels + descriptions in selectable languages, claims (property → value), sitelinks. 110M+ entities, CC0. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
Register the MCP server in PolicyLayer and add a rule for 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 Mcp. Nothing to install.
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 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 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.
wikidata.entity is provided by the MCP server (@2sio/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →