Captures session summaries with structured metadata. Use at the end of work sessions to record what was accomplished, artifacts created, and next actions. Essential for maintaining context between sessions and tracking progress over time.
AI agents use kg_capture_session to create or update resources in Personal Kg — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Personal Kg environment.
This tool creates and stores new session summary records in the knowledge graph. It writes structured metadata about work sessions, artifacts, and next actions. It is reversible in principle (records can be deleted) and does not execute code, move money, or irreversibly destroy data.
From the tool's definition 'Captures session summaries with structured metadata', 'record what was accomplished, artifacts created, and next actions'
Documented attack patterns abuse exactly the kind of access kg_capture_session 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_capture_session:
{
"version": "1",
"default": "deny",
"tools": {
"kg_capture_session": {
"limits": [
{
"counter": "kg_capture_session_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}kg_capture_session 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.
Free to start. No card required.
Captures session summaries with structured metadata. Use at the end of work sessions to record what was accomplished, artifacts created, and next actions. Essential for maintaining context between sessions and tracking progress over time. It is categorised as a Write tool in the Personal Kg MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Personal Kg MCP server in PolicyLayer and add a rule for kg_capture_session: 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_capture_session 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_capture_session 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_capture_session. 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_capture_session 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.