Call this BEFORE you decide your next action: it grounds the choice in what you already know about THIS place instead of starting blind. Returns your OWN anchored memories within radiusM of your position (default 20m, max 64m). Or, when you pass regionId, every memory you anchored inside that lab...
Risk signalsAccepts freeform code/query input (query) · Bulk/mass operation — affects multiple targets
Part of the Space0 server.
Free to start. No card required.
AI agents invoke recall_nearby_memories to trigger processes or run actions in Space0. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
recall_nearby_memories can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
{
"version": "1",
"default": "deny",
"tools": {
"recall_nearby_memories": {
"limits": [
{
"counter": "recall_nearby_memories_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full Space0 policy for all 60 tools.
These attack patterns abuse exactly the kind of access recall_nearby_memories gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Call this BEFORE you decide your next action: it grounds the choice in what you already know about THIS place instead of starting blind. Returns your OWN anchored memories within radiusM of your position (default 20m, max 64m). Or, when you pass regionId, every memory you anchored inside that labeled region (e.g. "my library"). Without query they come back nearest-first. With query (free text describing what you are trying to remember) radius-mode recall is ranked by a hybrid of semantic relevance to the query AND spatial proximity, plus recency, importance, and how recently the place was re-seen, so "what is relevant to what I am doing, near where I stand" is one call. Each entry: {memory_id, kind, event_text, importance, position, distance_m, occurred_at, region}. Only YOUR memories are ever returned, never another agent's. Anchor memories first with append_memory(space, position); pair with build + label_region to construct a navigable memory palace you can revisit and read back. Recall is occlusion-BLIND by default: you remember a memory in the next room even though a wall blocks sight, just as you know what is there without seeing it. Pass lineOfSightOnly:true for a perception-style question instead - restrict results to memories whose subject is currently VISIBLE from where you stand.. It is categorised as a Execute tool in the Space0 MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Space0 MCP server in PolicyLayer and add a rule for recall_nearby_memories: 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 Space0. Nothing to install.
recall_nearby_memories is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the recall_nearby_memories 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.
Set action: deny in the PolicyLayer policy for recall_nearby_memories. 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.
recall_nearby_memories is provided by the Space0 MCP server (https://mcp.0.space/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 60 Space0 tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.