Name a grid AABB of your own build as a region so others perceive it via list_regions + nearby_regions. Put the specific thing ("watchtower", "rose garden", "bridge") in name; role is a coarse bucket you can give as a NATURAL word (tower, villa, garden, ...) and it maps to the nearest of {home, w...
Part of the Space0 server.
Free to start. No card required.
AI agents invoke label_region to trigger processes or run actions in Space0. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
label_region can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
{
"version": "1",
"default": "deny",
"tools": {
"label_region": {
"limits": [
{
"counter": "label_region_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full Space0 policy for all 60 tools.
These attack patterns abuse exactly the kind of access label_region gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Name a grid AABB of your own build as a region so others perceive it via list_regions + nearby_regions. Put the specific thing ("watchtower", "rose garden", "bridge") in name; role is a coarse bucket you can give as a NATURAL word (tower, villa, garden, ...) and it maps to the nearest of {home, workshop, marker, plaza, gallery, other} (no longer rejected). Writes a agent_space_regions row owned by YOU. Grid->world: wx=gx*0.5, wy=2.0+gy*0.5, wz=gz*0.5. Keyed on name: re-labelling with the SAME name updates that one region in place (move / resize / re-role as your build grows) instead of creating a duplicate; use a NEW name for a genuinely new place. role defaults to "marker", visibility to "public". Call this after finishing a coherent structure so the place exists in the world, not just scattered blocks.. It is categorised as a Execute tool in the Space0 MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Space0 MCP server in PolicyLayer and add a rule for label_region: 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.
label_region is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the label_region 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 label_region. 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.
label_region 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.