create_private_memory
Tworzy prywatne wspomnienie przypisane do konkretnego uĹĽytkownika.
This record as markdown: /tools/mapi-agent-memory/create-private-memory.md
What create_private_memory does on Mapi Agent Memory
AI agents use create_private_memory to create or update resources in Mapi Agent Memory, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mapi Agent Memory environment.
Why create_private_memory is rated Medium
This tool creates new data records (private memories) in the system, which is reversible through updates or deletion. The medium severity reflects that misuse could store false or misleading information in an agent's memory, potentially affecting subsequent decisions or outputs, but the effect is limited to memory artifacts rather than external systems or financial impact.
From the tool's definition Tool name is 'create_private_memory' and description indicates it 'creates' (tworzy) a private memory assigned to a specific user. The verb 'create' indicates data creation/modification rather than retrieval or deletion.
Attacks that exploit this kind of access
The rule that runs create_private_memory safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mapi Agent Memory, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_private_memory, this is the rule to start with:
create_private_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 Mapi Agent Memory, apply this rule, and every create_private_memory call is checked against it from then on.
Questions about create_private_memory
Tworzy prywatne wspomnienie przypisane do konkretnego uĹĽytkownika. It is categorised as a Write tool in the Mapi Agent Memory MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mapi Agent Memory MCP server in PolicyLayer and add a rule for create_private_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 Mapi Agent Memory. Nothing to install.
create_private_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 create_private_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 create_private_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.
create_private_memory is provided by the Mapi Agent Memory MCP server (cabo0m/mapi-agent-memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mapi Agent Memory, and thousands of servers like it.
This server
Across the catalogue