Low Risk

search_entity

Search for a Wikidata entity ID by its query.

How to control search_entity ↓

AI agents call search_entity to retrieve information from Wikidata MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool performs a search operation to retrieve Wikidata entity identifiers based on a query string. Searches are inherently read operations that retrieve public data without modifying, deleting, or executing code. The blast radius of misuse is minimal—an attacker could gather information about entities, but cannot alter data or trigger harmful operations.

From the tool's definition Tool name 'search_entity' and description 'Search for a Wikidata entity ID by its query' indicate a retrieval/query operation with no side effects.

Documented attack patterns abuse exactly the kind of access search_entity gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Wikidata MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_entity:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_entity": {}
  }
}

search_entity is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Wikidata MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the search_entity tool do? +

Search for a Wikidata entity ID by its query. It is categorised as a Read tool in the Wikidata MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_entity? +

Register the Wikidata MCP Server MCP server in PolicyLayer and add a rule for search_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 Wikidata MCP Server. Nothing to install.

What risk level is search_entity? +

search_entity is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit search_entity? +

Yes. Add a rate_limit block to the search_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.

How do I block search_entity completely? +

Set action: deny in the PolicyLayer policy for search_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.

What MCP server provides search_entity? +

search_entity is provided by the Wikidata MCP Server MCP server (zzaebok/mcp-wikidata). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Wikidata MCP Server tool call.

Deterministic rules across all 5 Wikidata MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

5 Wikidata MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.