Find conversations with no recent memory activity.
AI agents call conversation_stale to retrieve information from Rekal without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a passive search/filter operation to identify stale conversations based on activity timestamps. It does not modify, delete, or execute any side effects; it merely queries the local SQLite database and returns results. Classification as Read is appropriate with low severity since misuse would only expose metadata about conversation activity patterns.
From the tool's definition Tool description states 'Find conversations with no recent memory activity' — a query operation that retrieves or lists data matching a staleness criterion with no modification or deletion.
Documented attack patterns abuse exactly the kind of access conversation_stale gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Rekal, and nothing reaches the server without passing your rules. This is the rule we recommend for conversation_stale:
{
"version": "1",
"default": "deny",
"tools": {
"conversation_stale": {}
}
}conversation_stale 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.
Find conversations with no recent memory activity. It is categorised as a Read tool in the Rekal MCP Server, which means it retrieves data without modifying state.
Register the Rekal MCP server in PolicyLayer and add a rule for conversation_stale: 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 Rekal. Nothing to install.
conversation_stale 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 conversation_stale 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 conversation_stale. 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.
conversation_stale is provided by the Rekal MCP server (janbjorge/rekal). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Rekal, 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.
21 Rekal tools catalogued and risk-classified — across an index of 43,000+ MCP servers.