kg_evaluate_retrieval
Check how well a set of kg_search results is backed by the knowledge graph before you answer from them. Pass the chunk ids kg_search returned. Each chunk gets a bucket: authored-grounded (backed by links people authored), extracted-high-conf or extracted-low-conf (backed by links inferred from te...
This record as markdown: /tools/io-stablebaseline-sb/kg-evaluate-retrieval.md
What kg_evaluate_retrieval does on Stable Baseline
AI agents use kg_evaluate_retrieval to create or update resources in Stable Baseline, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Stable Baseline environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
chunkIds | array | Yes | The chunks to assess: the chunk_id of each kg_search result. |
Parameters from the server's own tool schema.
Why kg_evaluate_retrieval is rated Medium
An AI agent can call kg_evaluate_retrieval faster than any human can review: one bad instruction and it creates or modifies resources in Stable Baseline by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs kg_evaluate_retrieval 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_evaluate_retrieval, this is the rule to start with:
kg_evaluate_retrieval stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_evaluate_retrieval call is checked against it from then on.
Questions about kg_evaluate_retrieval
Check how well a set of kg_search results is backed by the knowledge graph before you answer from them. Pass the chunk ids kg_search returned. Each chunk gets a bucket: authored-grounded (backed by links people authored), extracted-high-conf or extracted-low-conf (backed by links inferred from text, with high or low confidence), or no-support (nothing in the graph backs it). Also returns the overall distribution, dominant_bucket, recommend_refusal and a short agent_summary. Use it to decide whether to answer confidently, add a caveat, or decline. It only reads stored information: no AI call is made, so it is quick and adds no cost. It is categorised as a Write tool in the Stable Baseline MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
kg_evaluate_retrieval accepts 1 parameter: chunkIds. Required: chunkIds. 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_evaluate_retrieval: 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_evaluate_retrieval is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the kg_evaluate_retrieval 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_evaluate_retrieval. 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_evaluate_retrieval 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