log_memory · OmniHub MCP: Risk & Policy

WHAT IT DOES

What log_memory does on OmniHub

AI agents use log_memory to create or update resources in OmniHub — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your OmniHub environment.

WHY IT NEEDS A POLICY

Why log_memory needs a policy

This tool writes new memory entries to the personal memory store. It creates data reversibly (memories can be deleted or edited via sibling tools), making it a Write operation. Misuse could result in storing false, misleading, or sensitive information in the agent's memory system, hence medium severity.

From the tool's definition 'Logs a professional memory, thought, or decision' — creates/stores new data entries

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

log_memory Rate-limited

log_memory 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "log_memory": {
      "limits": [
        {
          "counter": "log_memory_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches OmniHub, so you can run agents against it safely.

FAQ

Questions about log_memory

What does the log_memory tool do? +

Logs a professional memory, thought, or decision. It is categorised as a Write tool in the OmniHub MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on log_memory? +

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

What risk level is log_memory? +

log_memory is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit log_memory? +

Yes. Add a rate_limit block to the log_memory 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 log_memory completely? +

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

log_memory is provided by the OmniHub MCP server (malharrrr/omnihub). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.