kg_get_entity
Fetch a KG entity by id or name, with 1-hop neighbours.
This record as markdown: /tools/io-stablebaseline-sb/kg-get-entity.md
What kg_get_entity does on Stable Baseline
AI agents call kg_get_entity to retrieve information from Stable Baseline 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 | — | |
entityId | string | — |
Parameters from the server's own tool schema.
Why kg_get_entity is rated Low
This tool retrieves information from the Knowledge Graph (entity data and related neighbours) without creating, modifying, deleting, or executing any operations. It is a pure query operation with no side effects, fitting the Read category.
From the tool's definition Tool name 'kg_get_entity' and description 'Fetch a KG entity by id or name, with 1-hop neighbours' indicate data retrieval only. The verb 'Fetch' and the read-only nature of querying a Knowledge Graph entity without modification confirm no side effects.
Attacks that exploit this kind of access
The rule that runs kg_get_entity safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Stable Baseline, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For kg_get_entity, this is the rule to start with:
kg_get_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 Stable Baseline, apply this rule, and every kg_get_entity call is checked against it from then on.
Questions about kg_get_entity
Fetch a KG entity by id or name, with 1-hop neighbours. It is categorised as a Read tool in the Stable Baseline MCP Server, which means it retrieves data without modifying state.
kg_get_entity accepts 2 parameters: name, entityId. The full parameter table on this page comes from the server's own tool schema.
Register the Stable Baseline MCP server in PolicyLayer and add a rule for kg_get_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 Stable Baseline. Nothing to install.
kg_get_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_get_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_get_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_get_entity is provided by the Stable Baseline MCP server (https://api.stablebaseline.io/functions/v1/cloud-serve/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Stable Baseline, and thousands of servers like it.
This server
Across the catalogue