Persistent memory for MacPilot. Store actions to learn patterns, recall context across sessions, update user preferences, or check stats. Use
AI agents use pilotgentic_memory to create or update resources in PilotGentic — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your PilotGentic environment.
This tool writes to a persistent memory system that tracks user actions, preferences, and session context. While reversible (preferences can be changed, records updated), the high confidence is warranted by explicit mentions of store/update operations.
From the tool's definition The tool stores, updates, and modifies persistent data: 'Store actions', 'recall context across sessions', 'update user preferences'. These are write operations that create or modify data reversibly.
Attacks that exploit this kind of access
Persistent memory for MacPilot. Store actions to learn patterns, recall context across sessions, update user preferences, or check stats. Use. It is categorised as a Write tool in the PilotGentic MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the PilotGentic MCP server in PolicyLayer and add a rule for pilotgentic_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 PilotGentic. Nothing to install.
pilotgentic_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 pilotgentic_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 pilotgentic_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.
pilotgentic_memory is provided by the PilotGentic MCP server (@pilotgentic/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →