Create a summary of context items and link them to the summary
AI agents use create-summary to create or update resources in Memory MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Memory MCP environment.
The tool creates new summary records and establishes links/relationships between data entities (context items and summaries). This is a reversible write operation—summaries can be deleted or modified later. It does not delete data irreversibly, execute arbitrary code, move money, or merely read existing data.
From the tool's definition Tool name 'create-summary' combined with description 'Create a summary of context items and link them to the summary' indicates data creation and modification.
Documented attack patterns abuse exactly the kind of access create-summary gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Memory MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for create-summary:
{
"version": "1",
"default": "deny",
"tools": {
"create-summary": {
"limits": [
{
"counter": "create-summary_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create-summary 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 summary of context items and link them to the summary. It is categorised as a Write tool in the Memory MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Memory MCP server in PolicyLayer and add a rule for create-summary: 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 MCP. Nothing to install.
create-summary 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-summary 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-summary. 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-summary is provided by the Memory MCP server (jamesanz/memory-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Memory MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
10 Memory MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.