Search for entities in Wikidata by text query
AI agents call search_entities to retrieve information from MCP Wikidata Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only search operation against Wikidata. It retrieves information based on user input but does not create, modify, delete, or execute arbitrary code. The ability to search an open knowledge base like Wikidata carries minimal risk; the worst case is an agent performs many queries or extracts unintended information, which is low-severity compared to other categories.
From the tool's definition Tool description states 'Search for entities in Wikidata by text query' - a retrieval operation with no data modification or external side effects. The verb 'search' indicates querying/lookup functionality.
Attacks that exploit this kind of access
Search for entities in Wikidata by text query. It is categorised as a Read tool in the MCP Wikidata Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Wikidata Server MCP server in PolicyLayer and add a rule for search_entities: 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 Wikidata Server. Nothing to install.
search_entities 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 search_entities 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 search_entities. 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.
search_entities is provided by the MCP Wikidata Server MCP server (joelgombin/mcp-wikidata). 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 →