Create a new memory in the agent memories system
AI agents use create_memory to create or update resources in Agentic Tools MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Agentic Tools MCP Server environment.
This tool creates new data (memory records) in a reversible manner. It falls clearly into the Write category as it modifies state by adding entries to the agent's memory storage. Severity is low because memory creation in an agentic task management system has minimal blast radius—it stores information without executing external operations, deleting data, or causing financial consequences.
From the tool's definition Tool name is 'create_memory' and description states 'Create a new memory in the agent memories system'. The verb 'Create' indicates data creation.
Documented attack patterns abuse exactly the kind of access create_memory gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Agentic Tools MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_memory:
{
"version": "1",
"default": "deny",
"tools": {
"create_memory": {
"limits": [
{
"counter": "create_memory_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_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.
Free to start. No card required.
Create a new memory in the agent memories system. It is categorised as a Write tool in the Agentic Tools MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Agentic Tools MCP Server MCP server in PolicyLayer and add a rule for create_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 Agentic Tools MCP Server. Nothing to install.
create_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_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_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_memory is provided by the Agentic Tools MCP Server MCP server (pimzino/agentic-tools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 29 Agentic Tools MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
29 Agentic Tools MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.