This record as markdown: /tools/io-github-dreamrec-livepilot/memory-favorite.md
What memory_favorite does on Livepilot
AI agents use memory_favorite 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 memory_favorite is rated Medium
This tool modifies stored data by starring and/or rating a technique — a reversible write operation with minimal blast radius since it only affects user preference metadata within the application.
From the tool's definition Star and/or rate a technique (rating 0-5)
Attacks that exploit this kind of access
The rule that runs memory_favorite 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_favorite, this is the rule to start with:
memory_favorite 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 memory_favorite call is checked against it from then on.
Questions about memory_favorite
Star and/or rate a technique (rating 0-5). 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 memory_favorite: 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_favorite 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 memory_favorite 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_favorite. 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_favorite 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