Save teammate session memory to disk
AI agents use teammate_save_memory to create or update resources in Claude Flow — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude Flow environment.
This tool writes or persists session memory to storage, which is a reversible data modification operation. It does not retrieve data (Read), execute arbitrary code or external operations (Execute), permanently delete data (Destructive), or involve financial transactions (Financial).
From the tool's definition Tool name 'teammate_save_memory' and description 'Save teammate session memory to disk' indicate creation/modification of persistent data via writing to disk.
Attacks that exploit this kind of access
Save teammate session memory to disk. It is categorised as a Write tool in the Claude Flow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claude Flow MCP server in PolicyLayer and add a rule for teammate_save_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 Claude Flow. Nothing to install.
teammate_save_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 teammate_save_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 teammate_save_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.
teammate_save_memory is provided by the Claude Flow MCP server (claude-flow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.