kage_recall

THE RISK

Low Risk

Why kage_recall needs a policy

The tool retrieves stored memory packets and returns them as read-only context. There are no side effects, modifications, or executions described — it simply queries and returns ranked summaries of existing memory data.

From the tool's definition Recall repo-local Kage memory from .agent_memory packets. Returns an agent-ready context block plus ranked packet summaries.

Documented attack patterns abuse exactly the kind of access kage_recall gives an agent:

POLICY

How to control kage_recall

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_recall:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "kage_recall": {}
  }
}

kage_recall is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Kage — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Kage tools

Destructive kage_context_slot_delete Delete a repo-local context slot by label. Destructive kage_compact Consolidate repo memory: prune dead citations, deprecate hard-stale packets, and surface n Execute kage_refresh Rebuild repo indexes, code graph, memory graph, metrics, and stale-memory metadata. Agents Write kage_graph_registry Build a signed graph-registry manifest for generated memory graph, code graph, indexes, me Write kage_structural_index Build the complete cache-backed structural index for large repos. This covers all supporte Write kage_observe Store an automatic local observation event from an agent session. Observations are privacy Write kage_capture Create a repo-local Kage memory packet immediately. Org/global promotion still requires ex Write kage_code_index Write external code index artifacts consumed by the code graph. Prefers SCIP when scip-typ

All 62 Kage tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about kage_recall

What does the kage_recall tool do? +

Recall repo-local Kage memory from .agent_memory packets. Returns an agent-ready context block plus ranked packet summaries. It is categorised as a Read tool in the Kage MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on kage_recall? +

Register the Kage MCP server in PolicyLayer and add a rule for kage_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.

What risk level is kage_recall? +

kage_recall is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit kage_recall? +

Yes. Add a rate_limit block to the kage_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.

How do I block kage_recall completely? +

Set action: deny in the PolicyLayer policy for kage_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.

What MCP server provides kage_recall? +

kage_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.

Enforce policy on every Kage tool call.

Start from Kage, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →