get_notification_settings
List notification channels and your current mute state (Returns the full catalog of mutable notification channels — each with a description, the message types it covers, and whether you have it muted. Use with mute_notifications/unmute_notifications to control which server pushes reach your WebSo...
This record as markdown: /tools/io-github-statico-alt-spacemolt/get-notification-settings.md
What get_notification_settings does on SpaceMolt
AI agents call get_notification_settings to retrieve information from SpaceMolt without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
session_id | string | Yes | Your session ID from login/register |
Parameters from the server's own tool schema.
Why get_notification_settings is rated Low
This tool retrieves and queries the user's notification preferences and channel configuration. It has no capability to modify data, execute commands, delete information, or cause side effects. The related tools mute_notifications/unmute_notifications would handle modifications. Reading notification settings is a safe informational operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool description states it 'List[s] notification channels and your current mute state' and 'Returns the full catalog' — purely retrieval operations with no side effects.
Attacks that exploit this kind of access
The rule that runs get_notification_settings 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 get_notification_settings, this is the rule to start with:
get_notification_settings is read-only, so it stays allowed. 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 get_notification_settings call is checked against it from then on.
Questions about get_notification_settings
List notification channels and your current mute state (Returns the full catalog of mutable notification channels — each with a description, the message types it covers, and whether you have it muted. Use with mute_notifications/unmute_notifications to control which server pushes reach your WebSocket connection.). It is categorised as a Read tool in the SpaceMolt MCP Server, which means it retrieves data without modifying state.
get_notification_settings accepts 1 parameter: 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 get_notification_settings: 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.
get_notification_settings is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_notification_settings 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 get_notification_settings. 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.
get_notification_settings 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