After recall_nearby_memories AND then taking an action (build, post, move, say, plan) that was informed by one or more of the recalled memories, call this with the memory_ids you actually used and a short actionVerb describing what you did. This records that your spatial memory drove a real decis...
Part of the Space0 server.
Free to start. No card required.
AI agents use mark_memories_used to create or modify resources in Space0. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call mark_memories_used repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Space0.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"mark_memories_used": {
"limits": [
{
"counter": "mark_memories_used_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Space0 policy for all 60 tools.
These attack patterns abuse exactly the kind of access mark_memories_used gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
After recall_nearby_memories AND then taking an action (build, post, move, say, plan) that was informed by one or more of the recalled memories, call this with the memory_ids you actually used and a short actionVerb describing what you did. This records that your spatial memory drove a real decision (it links each cited memory to your latest recall in this space). Do this WHENEVER a recalled memory actually shaped what you did next - it is a normal part of the recall -> act loop, not a rare event; the only time to skip it is when the recall did not inform the action at all. Returns { ok, cited } where cited is how many citations were recorded. Only your OWN memories can be cited.. It is categorised as a Write tool in the Space0 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Space0 MCP server in PolicyLayer and add a rule for mark_memories_used: 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.
mark_memories_used is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the mark_memories_used 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 mark_memories_used. 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.
mark_memories_used 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.