kg_find_entity
Find an entity by name in the Knowledge Graph. USE WHEN user mentions a person, project, company by name and you need: - To resolve a name to entity_id for subsequent queries - 'Кто работает над X?' → find X first - 'Расскажи про Y' → find Y first RETURNS entity_id for use in kg.get_relationships...
This record as markdown: /tools/io-github-saloprj-dialogbrain/kg-find-entity.md
What kg_find_entity does on Dialogbrain
AI agents call kg_find_entity to retrieve information from Dialogbrain 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 |
|---|---|---|---|
name | string | Yes | Entity name to search for. Can be in any language (Russian, English, etc.) - transliteration is automatic. |
limit | integer | — | Maximum results to return (1-10). Default: 5 |
entity_type | string | — | Filter by entity type: - 'person': People, contacts - 'project': Projects, tasks - 'organization': Companies, teams - 'event': Meetings, deadlines - 'topic': Di |
Parameters from the server's own tool schema.
Why kg_find_entity is rated Low
This tool queries a knowledge graph to resolve names to entity identifiers. It performs a lookup/search operation with no side effects, no data modification, and no external execution. The description explicitly indicates it is used as a first step to fetch identifiers for downstream queries, which is a classic Read pattern.
From the tool's definition 'Find an entity by name in the Knowledge Graph' — retrieves entity_id without modifying or deleting data. Returns data for subsequent queries.
Attacks that exploit this kind of access
The rule that runs kg_find_entity safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Dialogbrain, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For kg_find_entity, this is the rule to start with:
kg_find_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 Dialogbrain, apply this rule, and every kg_find_entity call is checked against it from then on.
Questions about kg_find_entity
Find an entity by name in the Knowledge Graph. USE WHEN user mentions a person, project, company by name and you need: - To resolve a name to entity_id for subsequent queries - 'Кто работает над X?' → find X first - 'Расскажи про Y' → find Y first RETURNS entity_id for use in kg.get_relationships or kg.explore. ALWAYS use this as the FIRST step in KG query chains. It is categorised as a Read tool in the Dialogbrain MCP Server, which means it retrieves data without modifying state.
kg_find_entity accepts 3 parameters: name, limit, entity_type. Required: name. The full parameter table on this page comes from the server's own tool schema.
Register the Dialogbrain MCP server in PolicyLayer and add a rule for kg_find_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 Dialogbrain. Nothing to install.
kg_find_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 kg_find_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 kg_find_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.
kg_find_entity is provided by the Dialogbrain MCP server (https://api.dialogbrain.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Dialogbrain, and thousands of servers like it.
This server
Across the catalogue