memory_details

Fetch full structured details only for selected memory IDs after memory_search_index or memory_timeline narrows the set.

SERVERCoWork OS SOURCECoWork-OS/CoWork-OS

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cowork-os/memory-details.md

WHAT IT DOES

What memory_details does on CoWork OS

AI agents call memory_details to retrieve information from CoWork OS without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why memory_details is rated Low

The tool retrieves/fetches data for specific memory IDs. It has no side effects—it only reads structured details after a search or timeline query narrows the result set. This is a pure read operation with low blast radius even if misused.

From the tool's definition Fetch full structured details only for selected memory IDs

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs memory_details safely

PolicyLayer is an MCP gateway: it sits between your AI agents and CoWork OS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For memory_details, this is the rule to start with:

memory_details Allowed

memory_details is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "memory_details": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect CoWork OS, apply this rule, and every memory_details call is checked against it from then on.

FAQ

Questions about memory_details

What does the memory_details tool do? +

Fetch full structured details only for selected memory IDs after memory_search_index or memory_timeline narrows the set. It is categorised as a Read tool in the CoWork OS MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on memory_details? +

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

What risk level is memory_details? +

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

Can I rate-limit memory_details? +

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

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

memory_details is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on CoWork OS, and thousands of servers like it.

This server

All 342 CoWork OS tools →

Across the catalogue

get_event_details on CTFtime MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →