This record as markdown: /tools/io-github-dreamrec-livepilot/add-session-memory.md
What add_session_memory does on Livepilot
AI agents use add_session_memory to create or update resources in Livepilot, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Livepilot environment.
Why add_session_memory is rated Medium
This tool creates/stores data (Write category) but operates on ephemeral session state that is lost when the session ends, limiting persistence and blast radius. It does not execute external commands, delete data irreversibly, or cause financial impact. Severity is low because session memory modifications are reversible and scoped to the current session only.
From the tool's definition Tool name 'add_session_memory' and description 'Add an ephemeral session memory entry' indicate a CREATE operation that writes data to a temporary, in-session storage mechanism.
Attacks that exploit this kind of access
The rule that runs add_session_memory 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 add_session_memory, this is the rule to start with:
add_session_memory stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 add_session_memory call is checked against it from then on.
Questions about add_session_memory
Add an ephemeral session memory entry. It is categorised as a Write tool in the Livepilot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Livepilot MCP server in PolicyLayer and add a rule for add_session_memory: 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.
add_session_memory is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_session_memory 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 add_session_memory. 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.
add_session_memory 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