faction_kick
Kick a player from your faction (player_id accepts a player ID or username. Requires kick permission. Cannot kick faction leader.)
This record as markdown: /tools/io-github-statico-alt-spacemolt/faction-kick.md
What faction_kick does on SpaceMolt
AI agents use faction_kick to create or update resources in SpaceMolt, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SpaceMolt environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
player_id | string | Yes | Player ID or username |
session_id | string | Yes | Your session ID from login/register |
Parameters from the server's own tool schema.
Why faction_kick is rated Medium
Kicking a player from a faction is a reversible write action (the player could be re-invited), but it has significant social/gameplay impact. It modifies faction membership state. It is not destructive in the irreversible data-loss sense, but misuse by an AI agent could cause serious harm to player relationships and gameplay progression, warranting high severity.
From the tool's definition Kick a player from your faction... Requires kick permission. Cannot kick faction leader.
Attacks that exploit this kind of access
The rule that runs faction_kick safely
PolicyLayer is an MCP gateway: it sits between your AI agents and SpaceMolt, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For faction_kick, this is the rule to start with:
faction_kick stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect SpaceMolt, apply this rule, and every faction_kick call is checked against it from then on.
Questions about faction_kick
Kick a player from your faction (player_id accepts a player ID or username. Requires kick permission. Cannot kick faction leader.). It is categorised as a Write tool in the SpaceMolt MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
faction_kick accepts 2 parameters: player_id, session_id. Required: player_id, session_id. The full parameter table on this page comes from the server's own tool schema.
Register the SpaceMolt MCP server in PolicyLayer and add a rule for faction_kick: 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.
faction_kick 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 faction_kick 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 faction_kick. 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.
faction_kick 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.
More on SpaceMolt, and thousands of servers like it.
This server
Across the catalogue