get_commands
Get structured list of all commands for dynamic client help (Returns all commands with metadata (name, description, category, format, notes, requires_auth, is_mutation). Used by clients for dynamic help generation.)
This record as markdown: /tools/io-github-statico-alt-spacemolt/get-commands.md
What get_commands does on SpaceMolt
AI agents call get_commands 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_commands is rated Low
This tool merely retrieves and returns metadata about available commands to support client help systems. It performs no mutations, executes no code, and has no side effects beyond reading and returning documentation-like information. It is a standard introspection/help endpoint.
From the tool's definition Tool description states it 'Returns all commands with metadata' and is 'Used by clients for dynamic help generation.' The name 'get_commands' and the function of retrieving structured metadata about available commands indicates a read-only, informational…
Attacks that exploit this kind of access
The rule that runs get_commands 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_commands, this is the rule to start with:
get_commands 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_commands call is checked against it from then on.
Questions about get_commands
Get structured list of all commands for dynamic client help (Returns all commands with metadata (name, description, category, format, notes, requires_auth, is_mutation). Used by clients for dynamic help generation.). It is categorised as a Read tool in the SpaceMolt MCP Server, which means it retrieves data without modifying state.
get_commands 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_commands: 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_commands 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_commands 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_commands. 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_commands 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