Search public memories shared by all Purmemo users. This is the community knowledge base. WHEN TO USE: - User asks "what have other people saved about X?" - User wants to explore community knowledge - User asks to search public/shared memories - Looking for solutions others have found DOES NOT CO...
Risk signalsAccepts freeform code/query input (query)
Part of the Pūrmemo server.
Free to start. No card required.
AI agents call recall_public to retrieve information from Pūrmemo without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though recall_public only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"recall_public": {}
}
}See the full Pūrmemo policy for all 11 tools.
These attack patterns abuse exactly the kind of access recall_public gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Search public memories shared by all Purmemo users. This is the community knowledge base. WHEN TO USE: - User asks "what have other people saved about X?" - User wants to explore community knowledge - User asks to search public/shared memories - Looking for solutions others have found DOES NOT COUNT AGAINST RECALL QUOTA — public knowledge is free. FILTERS: - query: Semantic search query (uses vector similarity) - tag: Filter by tag - platform: Filter by source platform - sort: "recent" or "popular" (by recall count) EXAMPLE: recall_public({ query: "MCP server testing best practices" }) RETURNS: List of public memories with author attribution, relevance scores, and recall counts.. It is categorised as a Read tool in the Pūrmemo MCP Server, which means it retrieves data without modifying state.
Register the Pūrmemo MCP server in PolicyLayer and add a rule for recall_public: 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 Pūrmemo. Nothing to install.
recall_public 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 recall_public 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 recall_public. 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.
recall_public is provided by the Pūrmemo MCP server (purmemo/purmemo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 11 Pūrmemo tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.