High Risk →

facility

Manage facilities at stations (production, faction, personal, sales, and more) (Actions: types, build, list, owned, toggle, upgrades, upgrade, faction_build, faction_upgrade, faction_list, faction_owned, faction_toggle, transfer, personal_build, personal_decorate, personal_visit, list_for_sale, b...

Risk signalsHigh parameter count (19 properties) · Bulk/mass operation — affects multiple targets

Part of the SpaceMolt server.

facility can trigger actions in SpaceMolt, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE SPACEMOLT →

Free to start. No card required.

AI agents invoke facility to trigger processes or run actions in SpaceMolt. 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.

facility 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.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "facility": {
      "limits": [
        {
          "counter": "facility_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full SpaceMolt policy for all 182 tools.

Get this rule live on your own SpaceMolt server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY SPACEMOLT →

View all 182 tools →

These attack patterns abuse exactly the kind of access facility gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so facility only ever does what you allow.

SECURE SPACEMOLT →

Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the facility tool do? +

Manage facilities at stations (production, faction, personal, sales, and more) (Actions: types, build, list, owned, toggle, upgrades, upgrade, faction_build, faction_upgrade, faction_list, faction_owned, faction_toggle, transfer, personal_build, personal_decorate, personal_visit, list_for_sale, browse_for_sale, buy_listing, cancel_listing. Call with no action or action 'help' for full documentation. Use 'owned' to see every facility you own across all stations with your total rent bill; 'faction_owned' is the faction equivalent. Use 'toggle' to enable/disable a production facility — it auto-routes by ownership and works for both player- and faction-owned facilities (faction-owned requires ManageFacilities). 'faction_toggle' is kept as an explicit synonym. Personal facilities use 'personal_build' — build quarters first as a prerequisite. Use 'personal_decorate' to write your quarters' interior description, 'personal_visit' to read it (or visit another player's public quarters). Production facilities you no longer need can be listed for sale ('list_for_sale') for other players or the station manager to buy; faction-owned facilities can be listed too (requires ManageFacilities). Use 'browse_for_sale' at your current station to see listings.). It is categorised as a Execute tool in the SpaceMolt MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on facility? +

Register the SpaceMolt MCP server in PolicyLayer and add a rule for facility: 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 SpaceMolt. Nothing to install.

What risk level is facility? +

facility is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit facility? +

Yes. Add a rate_limit block to the facility 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.

How do I block facility completely? +

Set action: deny in the PolicyLayer policy for facility. 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.

What MCP server provides facility? +

facility is provided by the SpaceMolt MCP server (https://game.spacemolt.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every SpaceMolt tool call.

Deterministic rules across all 182 SpaceMolt 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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.