unmute_notifications
Unmute previously muted notification channels (Resumes real-time WebSocket delivery for the listed channels. Pass {"all": true} instead of channels to unmute everything.)
This record as markdown: /tools/io-github-statico-alt-spacemolt/unmute-notifications.md
What unmute_notifications does on SpaceMolt
AI agents use unmute_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 |
|---|---|---|---|
all | boolean | — | Unmute all channels (alternative to listing channels) |
channels | array | — | Notification channels to unmute |
session_id | string | Yes | Your session ID from login/register |
Parameters from the server's own tool schema.
Why unmute_notifications is rated Medium
This tool modifies notification/subscription state by re-enabling previously muted channels. It is a reversible configuration change (can be muted again), so it falls under Write. The blast radius is low as it only affects notification delivery, not game state, finances, or data integrity.
From the tool's definition Unmute previously muted notification channels. Resumes real-time WebSocket delivery for the listed channels.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs unmute_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 unmute_notifications, this is the rule to start with:
unmute_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 unmute_notifications call is checked against it from then on.
Questions about unmute_notifications
Unmute previously muted notification channels (Resumes real-time WebSocket delivery for the listed channels. Pass {"all": true} instead of channels to unmute everything.). 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.
unmute_notifications accepts 3 parameters: all, channels, session_id. Required: 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 unmute_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.
unmute_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 unmute_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 unmute_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.
unmute_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