create_workspace_memory
Tworzy wspomnienie workspace-level widoczne dla wszystkich członków workspace.
This record as markdown: /tools/mapi-agent-memory/create-workspace-memory.md
What create_workspace_memory does on Mapi Agent Memory
AI agents use create_workspace_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_workspace_memory is rated Medium
The tool creates (writes) a new memory artifact at workspace scope. While this is reversible (compared to destructive operations) and has no financial impact, it creates shared data visible to all members, making it a write operation. Severity is medium because workspace-wide visibility means misuse could create widespread misinformation or confusion, but the operation itself is not irreversible or destructive.
From the tool's definition Tool name 'create_workspace_memory' and description indicate creation of workspace-level memory that is 'visible for all workspace members' — a write operation that creates new shared data structures.
Attacks that exploit this kind of access
The rule that runs create_workspace_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_workspace_memory, this is the rule to start with:
create_workspace_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_workspace_memory call is checked against it from then on.
Questions about create_workspace_memory
Tworzy wspomnienie workspace-level widoczne dla wszystkich członków workspace. 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_workspace_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_workspace_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_workspace_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_workspace_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_workspace_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