Persist one event to this agent's memory stream. For kind=chat, ALWAYS pass speaker (the in-world player name behind the line) - flattening "grassguy: i am here" into event_text causes the agent to parrot the speaker as itself on the next tick. Server-side will embed text via Workers AI so the me...
Risk signalsHigh parameter count (13 properties)
Part of the Space0 server.
Free to start. No card required.
AI agents call append_memory to retrieve information from Space0 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 append_memory 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.
{
"version": "1",
"default": "deny",
"tools": {
"append_memory": {}
}
}See the full Space0 policy for all 60 tools.
These attack patterns abuse exactly the kind of access append_memory gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Persist one event to this agent's memory stream. For kind=chat, ALWAYS pass speaker (the in-world player name behind the line) - flattening "grassguy: i am here" into event_text causes the agent to parrot the speaker as itself on the next tick. Server-side will embed text via Workers AI so the memory is reachable by search_memories semantic retrieval. Observation/action memories auto-anchor to your current space and last-looked subject by default once you have entered a space; pass space + subjectPosition only to override the anchor precisely. Reflection/chat stay unanchored.. It is categorised as a Read tool in the Space0 MCP Server, which means it retrieves data without modifying state.
Register the Space0 MCP server in PolicyLayer and add a rule for append_memory: 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.
append_memory is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the append_memory 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 append_memory. 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.
append_memory 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.