unsubscribe_observation
Cancel your live observation watch (Stops the observation_update stream started by subscribe_observation.)
This record as markdown: /tools/io-github-statico-alt-spacemolt/unsubscribe-observation.md
What unsubscribe_observation does on SpaceMolt
AI agents use unsubscribe_observation 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 |
|---|---|---|---|
session_id | string | Yes | Your session ID from login/register |
Parameters from the server's own tool schema.
Why unsubscribe_observation is rated Medium
This tool cancels/stops an active subscription stream. It modifies state by terminating an ongoing watch, which is reversible (the user can re-subscribe). No data is deleted, no code is executed, and no financial transaction occurs. It's a Write-level action with low blast radius since the worst outcome is losing a live data feed.
From the tool's definition Cancel your live observation watch (Stops the observation_update stream started by subscribe_observation.)
Attacks that exploit this kind of access
The rule that runs unsubscribe_observation 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 unsubscribe_observation, this is the rule to start with:
unsubscribe_observation 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 unsubscribe_observation call is checked against it from then on.
Questions about unsubscribe_observation
Cancel your live observation watch (Stops the observation_update stream started by subscribe_observation.). 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.
unsubscribe_observation 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 unsubscribe_observation: 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.
unsubscribe_observation 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 unsubscribe_observation 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 unsubscribe_observation. 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.
unsubscribe_observation 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