Low Risk

cybersync_get_memory

Get Claude memory entries from PostgreSQL (ingested from memory.db).

How to control cybersync_get_memory ↓

What cybersync_get_memory does on OmniWire

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

Low Risk

Why cybersync_get_memory needs a policy

This tool queries and retrieves memory entries from a database without modifying, deleting, or executing operations. However, severity is elevated to 'medium' rather than 'low' because memory entries may contain sensitive information, credentials, or private conversation history that could be exploited if an AI agent queries and exfiltrates this data to unauthorized parties.

From the tool's definition The tool retrieves Claude memory entries from PostgreSQL via 'Get' operation and queries a database. It performs data retrieval with 'no side effects' as stated in the Read category definition.

Documented attack patterns abuse exactly the kind of access cybersync_get_memory gives an agent:

How to control cybersync_get_memory

PolicyLayer is an MCP gateway — it sits between your AI agents and OmniWire, and nothing reaches the server without passing your rules. This is the rule we recommend for cybersync_get_memory:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "cybersync_get_memory": {}
  }
}

cybersync_get_memory is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register OmniWire — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about cybersync_get_memory

What does the cybersync_get_memory tool do? +

Get Claude memory entries from PostgreSQL (ingested from memory.db). It is categorised as a Read tool in the OmniWire MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on cybersync_get_memory? +

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

What risk level is cybersync_get_memory? +

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

Can I rate-limit cybersync_get_memory? +

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

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

cybersync_get_memory is provided by the OmniWire MCP server (voidchecksum/omniwire). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every OmniWire tool call.

Start from OmniWire, 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.

88 OmniWire tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.