Promote (ascend) a fact / leaf / file_summary from files.db to
AI agents use files_promote to create or update resources in M3 Memory — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your M3 Memory environment.
The tool modifies the organizational state or metadata of stored data by promoting facts/files from one logical location to another within the memory layer. This is a reversible write operation (data is reorganized but not deleted). It does not create new data (Write rather than Create), does not execute arbitrary code (not Execute), and does not irreversibly delete data (not Destructive).
From the tool's definition Tool name 'files_promote' and description 'Promote (ascend) a fact / leaf / file_summary from files.db to' indicates modifying data state by moving/promoting items within a database.
Documented attack patterns abuse exactly the kind of access files_promote gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and M3 Memory, and nothing reaches the server without passing your rules. This is the rule we recommend for files_promote:
{
"version": "1",
"default": "deny",
"tools": {
"files_promote": {
"limits": [
{
"counter": "files_promote_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}files_promote 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.
Promote (ascend) a fact / leaf / file_summary from files.db to. It is categorised as a Write tool in the M3 Memory MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the M3 Memory MCP server in PolicyLayer and add a rule for files_promote: 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 M3 Memory. Nothing to install.
files_promote 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 files_promote 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 files_promote. 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.
files_promote is provided by the M3 Memory MCP server (skynetcmd/m3-memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from M3 Memory, 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.
43 M3 Memory tools catalogued and risk-classified — across an index of 43,000+ MCP servers.