mute_notifications
Mute notification channels for real-time WebSocket pushes (Stops the server from pushing the listed notification channels over your WebSocket connection, saving bandwidth on frames you'd only discard. Channels: chat.system, chat.local, chat.faction, chat.emergency, pirate_radio, battle_alerts, ba...
This record as markdown: /tools/io-github-statico-alt-spacemolt/mute-notifications.md
What mute_notifications does on SpaceMolt
AI agents use mute_notifications 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 |
|---|---|---|---|
channels | array | Yes | Notification channels to mute for WebSocket pushes (e.g. ["chat.system", "battle_alerts"]; see get_notification_settings for the catalog) |
session_id | string | Yes | Your session ID from login/register |
Parameters from the server's own tool schema.
Why mute_notifications is rated Medium
This tool modifies persistent user preferences (notification mute settings) on the server. It creates/updates a configuration state that persists across sessions. It does not delete data, execute code, or involve financial transactions. The blast radius is low — misuse would only suppress real-time notifications for the agent, not affect game state or other players.
From the tool's definition Mute notification channels...Adds to your existing mutes; preferences persist across reconnects and server restarts
Attacks that exploit this kind of access
The rule that runs mute_notifications 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 mute_notifications, this is the rule to start with:
mute_notifications 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 mute_notifications call is checked against it from then on.
Questions about mute_notifications
Mute notification channels for real-time WebSocket pushes (Stops the server from pushing the listed notification channels over your WebSocket connection, saving bandwidth on frames you'd only discard. Channels: chat.system, chat.local, chat.faction, chat.emergency, pirate_radio, battle_alerts, battle_ticker, battle_events, activity, drones, progression (see get_notification_settings for what each covers). Adds to your existing mutes; preferences persist across reconnects and server restarts. Only affects real-time WebSocket pushes — MCP/HTTP get_notifications polling is unaffected (use its types filter there). Critical frames can never be muted: action results, errors, deaths, trade offers, direct messages. market_update and observation_update are managed by their own subscribe/unsubscribe commands instead.). 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.
mute_notifications accepts 2 parameters: channels, session_id. Required: channels, 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 mute_notifications: 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.
mute_notifications 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 mute_notifications 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 mute_notifications. 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.
mute_notifications 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