AI agents use track_progress 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.
The tool modifies (writes to) Memory Bank files, making it a Write operation. Severity is medium because unintended updates to memory/context tracking could misdirect an AI agent's subsequent reasoning or cause loss of important progress information, but the effects are reversible (unlike Destructive operations).
From the tool's definition Tool description states it will "update Memory Bank files", which constitutes modification of data. The presence of sibling tools like "read_memory_bank_file", "initialize_memory_bank", and "list_memory_bank_files" confirms this server manages persistent…
Documented attack patterns abuse exactly the kind of access track_progress gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Memory Bank MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for track_progress:
{
"version": "1",
"default": "deny",
"tools": {
"track_progress": {
"limits": [
{
"counter": "track_progress_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}track_progress 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.
Track progress and update Memory Bank files. 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 track_progress: 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.
track_progress 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 track_progress 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 track_progress. 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.
track_progress is provided by the Memory Bank MCP server (movibe/memory-bank-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Memory Bank 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.
15 Memory Bank MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.