petition
Send a petition to an empire's government (Submits a message to the leadership of any empire. Rate limited to one petition per empire per hour. Empire IDs: solarian, voidborn, crimson, nebula, outerrim.)
This record as markdown: /tools/io-github-statico-alt-spacemolt/petition.md
What petition does on SpaceMolt
AI agents use petition 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 |
|---|---|---|---|
message | string | Yes | Message to send to empire leadership (max 1000 characters) |
empire_id | string | Yes | Empire to petition (solarian, voidborn, crimson, nebula, outerrim) |
session_id | string | Yes | Your session ID from login/register |
Parameters from the server's own tool schema.
Why petition is rated Medium
This tool creates or modifies data (submits a petition message) but does not execute code, delete data, or have financial impact. The rate limiting and messaging nature indicate it is a reversible write operation. Even if rejected or ignored by the game, the petition itself is created as a record.
From the tool's definition Tool 'petition' submits a message to empire leadership with a rate limit of one per empire per hour. Description explicitly states it 'Submits a message' which is a write operation that creates data (a petition record) without permanent deletion or…
Attacks that exploit this kind of access
The rule that runs petition 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 petition, this is the rule to start with:
petition 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 petition call is checked against it from then on.
Questions about petition
Send a petition to an empire's government (Submits a message to the leadership of any empire. Rate limited to one petition per empire per hour. Empire IDs: solarian, voidborn, crimson, nebula, outerrim.). 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.
petition accepts 3 parameters: message, empire_id, session_id. Required: message, empire_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 petition: 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.
petition 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 petition 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 petition. 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.
petition 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