Retrieves relevant past context for a given query. Returns brief summaries of related decisions, insights, and open questions. Perfect for proactive context injection before starting work on a topic.
AI agents call kg_get_relevant_context to retrieve information from Personal Kg without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool fetches and surfaces historical decision context, insights, and open questions to inform current work. It performs no modifications, deletions, or irreversible operations. The retrieval of stored knowledge is a classic Read operation with minimal blast radius, as misuse would at worst surface incorrect or sensitive historical data rather than alter state or trigger external actions.
From the tool's definition Tool description states 'Retrieves relevant past context' and 'Returns brief summaries' — these are read-only query operations with no side effects.
Documented attack patterns abuse exactly the kind of access kg_get_relevant_context gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Personal Kg, and nothing reaches the server without passing your rules. This is the rule we recommend for kg_get_relevant_context:
{
"version": "1",
"default": "deny",
"tools": {
"kg_get_relevant_context": {}
}
}kg_get_relevant_context is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Retrieves relevant past context for a given query. Returns brief summaries of related decisions, insights, and open questions. Perfect for proactive context injection before starting work on a topic. It is categorised as a Read tool in the Personal Kg MCP Server, which means it retrieves data without modifying state.
Register the Personal Kg MCP server in PolicyLayer and add a rule for kg_get_relevant_context: 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 Personal Kg. Nothing to install.
kg_get_relevant_context 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_relevant_context 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_relevant_context. 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_relevant_context is provided by the Personal Kg MCP server (tomschell/personal-kg-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Personal Kg, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
18 Personal Kg tools catalogued and risk-classified — across an index of 43,000+ MCP servers.