search_open_entities
Search bounded Wikidata entity metadata through the public Action API. Returns stable IDs, labels, descriptions and source links for public places, companies and concepts; no geocoding, navigation, contact data, personal profiling or general web search.
This record as markdown: /tools/io-github-davidmosiah-delx-mcp-a2a/search-open-entities.md
What search_open_entities does on Delx Mcp A2a
AI agents call search_open_entities to retrieve information from Delx Mcp A2a 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 |
|---|---|---|---|
query | string | Yes | Entity query, 1-120 characters. |
timeout | integer | — | Upstream timeout in seconds. |
max_records | integer | — | Maximum number of Wikidata entity results. |
Parameters from the server's own tool schema.
Why search_open_entities is rated Low
This is a read-only search operation against public Wikidata entities. It queries and returns metadata without modifying data, executing code, or accessing sensitive information. The exclusions confirm it does not provide navigation, contact details, or personal data. Misuse would have minimal blast radius—an agent could only retrieve publicly available reference information about entities.
From the tool's definition Tool description states it 'Search[es] bounded Wikidata entity metadata' and 'Returns stable IDs, labels, descriptions and source links' with explicit exclusions: 'no geocoding, navigation, contact data, personal profiling or general web search.' The tool…
Attacks that exploit this kind of access
The rule that runs search_open_entities safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx Mcp A2a, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_open_entities, this is the rule to start with:
search_open_entities 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 Delx Mcp A2a, apply this rule, and every search_open_entities call is checked against it from then on.
Questions about search_open_entities
Search bounded Wikidata entity metadata through the public Action API. Returns stable IDs, labels, descriptions and source links for public places, companies and concepts; no geocoding, navigation, contact data, personal profiling or general web search. It is categorised as a Read tool in the Delx Mcp A2a MCP Server, which means it retrieves data without modifying state.
search_open_entities accepts 3 parameters: query, timeout, max_records. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Delx Mcp A2a MCP server in PolicyLayer and add a rule for search_open_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 Delx Mcp A2a. Nothing to install.
search_open_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_open_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_open_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_open_entities is provided by the Delx Mcp A2a MCP server (https://api.delx.ai/v1/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx Mcp A2a, and thousands of servers like it.
This server
Across the catalogue