Check whether repo memory, code graph, memory graph, and stale-memory state are ready for merge. Leads with a human summary of team memories invalidated by the current change — relay it to the developer.
AI agents call kage_pr_check to retrieve information from Kage without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
kage_pr_check is fundamentally a query and validation tool that examines the state of memory, code graphs, and metadata to determine merge-readiness. It produces a human-readable summary but does not create, modify, delete, or execute any operations.
From the tool's definition Tool performs checks and validation ("Check whether repo memory, code graph, memory graph, and stale-memory state are ready for merge") and relays information to developers ("relay it to the developer").
Documented attack patterns abuse exactly the kind of access kage_pr_check 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_pr_check:
{
"version": "1",
"default": "deny",
"tools": {
"kage_pr_check": {}
}
}kage_pr_check 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.
Check whether repo memory, code graph, memory graph, and stale-memory state are ready for merge. Leads with a human summary of team memories invalidated by the current change — relay it to the developer. It is categorised as a Read tool in the Kage MCP Server, which means it retrieves data without modifying state.
Register the Kage MCP server in PolicyLayer and add a rule for kage_pr_check: 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_pr_check 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 kage_pr_check 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_pr_check. 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_pr_check 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.