Recall Kage memory across every indexed repo in a local workspace and rank the combined hits. Use for cross-repo teammate knowledge and shared context.
AI agents call kage_workspace_recall 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.
The tool retrieves and ranks stored memory entries across multiple repositories without modifying or deleting anything. It is a read/query operation. Severity is medium because it queries across all indexed repos in a workspace, potentially exposing sensitive code knowledge, team learnings, and architectural context at scale — misuse could leak proprietary cross-repo information.
From the tool's definition 'Recall Kage memory across every indexed repo in a local workspace and rank the combined hits'
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access kage_workspace_recall 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_workspace_recall:
{
"version": "1",
"default": "deny",
"tools": {
"kage_workspace_recall": {}
}
}kage_workspace_recall 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.
Recall Kage memory across every indexed repo in a local workspace and rank the combined hits. Use for cross-repo teammate knowledge and shared context. 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_workspace_recall: 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_workspace_recall 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_workspace_recall 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_workspace_recall. 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_workspace_recall 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.