memory_audit

One-shot health report for the memory store: totals, category breakdown,

Server Loom jbarket/loom
Category Read
Risk class Low
Parameters 00 required

What memory_audit does on Loom

AI agents call memory_audit to retrieve information from Loom without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why memory_audit needs a policy

The tool generates a read-only audit/health report of the memory store, reporting totals and category breakdowns. This is a diagnostic/reporting operation with no side effects. Severity is low as it only reads metadata/statistics about memories rather than sensitive content itself.

From the tool's definition 'health report for the memory store: totals, category breakdown' — purely retrieves and reports statistics

Questions about memory_audit

What does the memory_audit tool do? +

One-shot health report for the memory store: totals, category breakdown,. It is categorised as a Read tool in the Loom MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on memory_audit? +

Register the Loom MCP server in PolicyLayer and add a rule for memory_audit: 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 Loom. Nothing to install.

What risk level is memory_audit? +

memory_audit is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit memory_audit? +

Yes. Add a rate_limit block to the memory_audit 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.

How do I block memory_audit completely? +

Set action: deny in the PolicyLayer policy for memory_audit. 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.

What MCP server provides memory_audit? +

memory_audit is provided by the Loom MCP server (jbarket/loom). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.