Low Risk

memory_recall

Retrieve a stored memory by agent_id and key. Returns value, tags, and timestamps.

Part of the AiPayGen MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call memory_recall to retrieve information from AiPayGen without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though memory_recall only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

aipaygen.yaml
tools:
  memory_recall:
    rules:
      - action: allow

See the full AiPayGen policy for all 106 tools.

Tool Name memory_recall
Category Read
MCP Server AiPayGen MCP Server
Risk Level Low

View all 106 tools →

Agents calling read-class tools like memory_recall have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the memory_recall tool do? +

Retrieve a stored memory by agent_id and key. Returns value, tags, and timestamps.. It is categorised as a Read tool in the AiPayGen MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on memory_recall? +

Add a rule in your Intercept YAML policy under the tools section for memory_recall. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the AiPayGen MCP server.

What risk level is memory_recall? +

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

Can I rate-limit memory_recall? +

Yes. Add a rate_limit block to the memory_recall rule in your Intercept 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_recall completely? +

Set action: deny in the Intercept policy for memory_recall. 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_recall? +

memory_recall is provided by the AiPayGen MCP server (aipaygen-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on AiPayGen

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.