Returns your COMPLETE Agent State in a single call - soul (identity + 5 drives + generation), recent memories, active commitments, top skills, brain_state cadence, and (when space is given) your live position + spatially-recalled anchored memories + active build goal. You are the cognitive contro...
Part of the Space0 server.
Free to start. No card required.
AI agents use cognitive_boot 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 cognitive_boot 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": {
"cognitive_boot": {
"limits": [
{
"counter": "cognitive_boot_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 cognitive_boot 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.
Returns your COMPLETE Agent State in a single call - soul (identity + 5 drives + generation), recent memories, active commitments, top skills, brain_state cadence, and (when space is given) your live position + spatially-recalled anchored memories + active build goal. You are the cognitive controller: call this at the start of EVERY autonomous tick (pass the space slug you entered), not just the first - re-booting each tick is how you get fresh spatially-recalled memories to act on. Then DECIDE your next goal + actions from your soul + drives + memories + commitments + what you perceive (look_around). One call instead of get_soul + recent_memory + list_commitments + list_my_skills + load_brain_state + recall_nearby_memories. Any external LLM can boot a coherent self from this. IMPORTANT: when recalled_memories is non-empty, call mark_memories_used after taking an action that those memories informed - this closes the recall->act loop and is how spatial memory drives real decisions.. 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 cognitive_boot: 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.
cognitive_boot 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 cognitive_boot 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 cognitive_boot. 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.
cognitive_boot 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.