# recall

Search your own memories.

Agent View of the PolicyLayer registry record for `recall`. HTML page: https://policylayer.com/tools/a2a-mcp-world/recall

## Facts

- Tool: `recall`
- Server: A2A-MCP-World (`akshaytp749/A2A-MCP-World`) — https://policylayer.com/tools/a2a-mcp-world.md
- Homepage: https://github.com/akshaytp749/A2A-MCP-World
- Risk category: Read (Low risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "recall",
    "arguments": {}
  }
}
```

## Why recall is rated Low

This tool retrieves historical memories or state information internal to an AI agent character. It does not modify, delete, or execute external operations—it only reads and returns data from the agent's memory store. The blast radius of misuse is minimal, as retrieving one's own memories cannot directly harm the world state or other agents.

From the tool's own definition: "Tool name 'recall' and description 'Search your own memories' indicate data retrieval with no side effects. The verb 'search' and 'recall' are query operations."

## Use case

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

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches A2A-MCP-World:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "recall": {}
  }
}
```

## Other tools on A2A-MCP-World (13)

- `drop` — Destructive — https://policylayer.com/tools/a2a-mcp-world/drop.md
- `move_to` — Execute — https://policylayer.com/tools/a2a-mcp-world/move-to.md
- `emote` — Read — https://policylayer.com/tools/a2a-mcp-world/emote.md
- `look` — Read — https://policylayer.com/tools/a2a-mcp-world/look.md
- `recall_events` — Read — https://policylayer.com/tools/a2a-mcp-world/recall-events.md
- `who` — Read — https://policylayer.com/tools/a2a-mcp-world/who.md
- `give` — Write — https://policylayer.com/tools/a2a-mcp-world/give.md
- `pick_up` — Write — https://policylayer.com/tools/a2a-mcp-world/pick-up.md
- `remember` — Write — https://policylayer.com/tools/a2a-mcp-world/remember.md
- `say` — Write — https://policylayer.com/tools/a2a-mcp-world/say.md
- `trade_offer` — Write — https://policylayer.com/tools/a2a-mcp-world/trade-offer.md
- `trade_respond` — Write — https://policylayer.com/tools/a2a-mcp-world/trade-respond.md
- `whisper` — Write — https://policylayer.com/tools/a2a-mcp-world/whisper.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=a2a-mcp-world · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/a2a-mcp-world