readAgentMemory

Retrieve previously stored data by key

SERVERNodebench SOURCEnodebench-mcp

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/io-github-homenshum-nodebench/readagentmemory.md

WHAT IT DOES

What readAgentMemory does on Nodebench

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

RISK

Why readAgentMemory is rated Low

This tool performs a read-only operation that queries or fetches stored data without modification or deletion. It matches the Read category definition of retrieving data with no side effects.

From the tool's definition Tool description states 'Retrieve previously stored data by key' which is a data retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs readAgentMemory safely

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

readAgentMemory Allowed

readAgentMemory 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": {
    "readAgentMemory": {}
  }
}

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

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

FAQ

Questions about readAgentMemory

What does the readAgentMemory tool do? +

Retrieve previously stored data by key. It is categorised as a Read tool in the Nodebench MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on readAgentMemory? +

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

What risk level is readAgentMemory? +

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

Can I rate-limit readAgentMemory? +

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

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

readAgentMemory is provided by the Nodebench MCP server (nodebench-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Nodebench, and thousands of servers like it.

This server

All 824 Nodebench tools →

Across the catalogue

The MCP Attack Database →

Guides

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