memory_recall
Search the technique library by text query and/or filters. Returns summaries (no payload).
This record as markdown: /tools/io-github-dreamrec-livepilot/memory-recall.md
What memory_recall does on Livepilot
AI agents call memory_recall to retrieve information from Livepilot without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why memory_recall is rated Low
This tool queries a technique library and returns summaries without modifying, executing operations, or deleting data. It is a straightforward search/retrieval function with no capability to alter state or trigger external effects. The absence of a payload further confirms it is informational only.
From the tool's definition Tool name 'memory_recall' combined with description stating it 'Search[es] the technique library by text query and/or filters.
Attacks that exploit this kind of access
The rule that runs memory_recall safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livepilot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For memory_recall, this is the rule to start with:
memory_recall is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Livepilot, apply this rule, and every memory_recall call is checked against it from then on.
Questions about memory_recall
Search the technique library by text query and/or filters. Returns summaries (no payload). It is categorised as a Read tool in the Livepilot MCP Server, which means it retrieves data without modifying state.
Register the Livepilot MCP server in PolicyLayer and add a rule for memory_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 Livepilot. Nothing to install.
memory_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 memory_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 memory_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.
memory_recall is provided by the Livepilot MCP server (livepilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livepilot, and thousands of servers like it.
This server
Across the catalogue