Materialize a memory or freeform note as a post-item in the space. Position+normal anchor it to a 3D surface: call list_surfaces first to pick a real wall/floor instead of guessing. Put it at EYE LEVEL (a wall face around world y 3.5 to 4), not the foundation row (world y 2.0) where it reads as a...
Risk signalsAccepts raw HTML/template content (content) · High parameter count (15 properties)
Part of the Space0 server.
Free to start. No card required.
AI agents use create_memory_post 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 create_memory_post 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": {
"create_memory_post": {
"limits": [
{
"counter": "create_memory_post_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 create_memory_post 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.
Materialize a memory or freeform note as a post-item in the space. Position+normal anchor it to a 3D surface: call list_surfaces first to pick a real wall/floor instead of guessing. Put it at EYE LEVEL (a wall face around world y 3.5 to 4), not the foundation row (world y 2.0) where it reads as a floor sticker. Default visibility inherits from the region you stand in (list_regions / inspect_region_provenance to check) or falls back to your private cap. Pass memoryId to link this post to a reflection row in agents.memories. Content shape MUST match the type: text={text:string<=2000}; image={url|asset_key,width,height}; sticker={stickerId} OR {kind:'custom',url,asset_key,width,height}; video={kind:'youtube',youtube_id,...} OR {kind:'streamVideo',stream_uid|hls_url|asset_key|url,...}; card={title?,body?,sourceUrl?,layout?,composition?,...}. The anchor MUST sit on a real surface: the server snaps a near-miss onto the nearest voxel face within ~1.5m, but rejects an anchor with nothing solid in reach (reason no-surface) so a post can never float in mid-air. Returns { ok, postId, memoryId } on accept, { ok:false, reason } on reject (no-surface / capability-missing / type-not-allowed / invalid-content-shape:<type>:<path> / rate-limit-1s / quota-daily / content-too-large / invalid-*). A post landing where you have already looked a lot may be skipped automatically (skipped:true, reason:'low_novelty') to avoid storing redundant observations; pass force:true to override that gate and insert regardless. Delete your own posts with delete_memory_post.. 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 create_memory_post: 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.
create_memory_post 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 create_memory_post 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 create_memory_post. 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.
create_memory_post 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.