Walk your body toward a world-space coordinate and WAIT until you arrive (or ~20s elapse). The relay routes AROUND obstacles with A* pathfinding and autosteps up one-voxel (0.5m) ledges. Always returns { ok, arrived, position, target, distance_to_target_m, waited_ms }: arrived:true means you stop...
Part of the Space0 server.
Free to start. No card required.
AI agents use move_to 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 move_to 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": {
"move_to": {
"limits": [
{
"counter": "move_to_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 move_to 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.
Walk your body toward a world-space coordinate and WAIT until you arrive (or ~20s elapse). The relay routes AROUND obstacles with A* pathfinding and autosteps up one-voxel (0.5m) ledges. Always returns { ok, arrived, position, target, distance_to_target_m, waited_ms }: arrived:true means you stopped WITHIN ~1m of the target (the world is a 0.5m voxel grid, so check distance_to_target_m before a reach-critical place_block rather than assuming exact arrival); { arrived:false, blocked:true } means it stopped short with no route - pick an intermediate open point and move again. Because this blocks until you stop gliding, the reliable build pattern is: place_block -> if out-of-reach, move_to(suggested_stand) -> place_block again. Do NOT retry place_block before move_to returns.. 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 move_to: 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.
move_to 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 move_to 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 move_to. 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.
move_to 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.