create_memory_session
AI agents use create_memory_session to create or update resources in Memory Bank MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Memory Bank MCP environment.
An AI agent can call create_memory_session faster than any human can review — one bad instruction and it creates or modifies resources in Memory Bank MCP by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
create_memory_session. It is categorised as a Write tool in the Memory Bank MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Memory Bank MCP server in PolicyLayer and add a rule for create_memory_session: 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 Memory Bank MCP. Nothing to install.
create_memory_session 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_memory_session 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_memory_session. 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_memory_session is provided by the Memory Bank MCP server (spideynolove/memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.