DB integrity + FTS5 sync check. Set rebuild=True to fix drift.
AI agents use files_health 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.
files_health performs database maintenance with optional modification capability. When rebuild=True is invoked, it modifies the FTS5 index and potentially database structures to restore consistency. This is a Write operation (modifies data/indices reversibly) rather than Read (it can change state) or Destructive (changes are reversible through rerun).
From the tool's definition Tool description states 'Set rebuild=True to fix drift', which indicates the ability to modify database state and rebuild indices. This is a reversible modification operation.
Documented attack patterns abuse exactly the kind of access files_health 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_health:
{
"version": "1",
"default": "deny",
"tools": {
"files_health": {
"limits": [
{
"counter": "files_health_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}files_health 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.
DB integrity + FTS5 sync check. Set rebuild=True to fix drift. 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_health: 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_health 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_health 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_health. 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_health 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.