Create or update a repo-local pinned context slot. Use for durable, high-signal repo guidance that should always be included without loading all memory.
AI agents use kage_context_slot_set to create or update resources in Kage — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kage environment.
The tool creates or updates a context slot, which is a reversible modification of repo-local configuration/guidance data. This falls under Write category—data is being created or modified but not irreversibly deleted. Severity is medium because misconfiguration could affect team guidance and agent behavior, but changes are recoverable and reviewable (consistent with the server's PR-tracked JSON design).
From the tool's definition Tool description states 'Create or update a repo-local pinned context slot', indicating it modifies stored configuration or metadata. The word 'create or update' is characteristic of Write operations that reversibly change data.
Documented attack patterns abuse exactly the kind of access kage_context_slot_set gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Kage, and nothing reaches the server without passing your rules. This is the rule we recommend for kage_context_slot_set:
{
"version": "1",
"default": "deny",
"tools": {
"kage_context_slot_set": {
"limits": [
{
"counter": "kage_context_slot_set_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}kage_context_slot_set 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.
Create or update a repo-local pinned context slot. Use for durable, high-signal repo guidance that should always be included without loading all memory. It is categorised as a Write tool in the Kage MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Kage MCP server in PolicyLayer and add a rule for kage_context_slot_set: 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 Kage. Nothing to install.
kage_context_slot_set 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 kage_context_slot_set 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 kage_context_slot_set. 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.
kage_context_slot_set is provided by the Kage MCP server (@kage-core/kage-graph-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Kage, 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.
62 Kage tools catalogued and risk-classified — across an index of 43,000+ MCP servers.