search_systems
Search for systems by name (Case-insensitive partial match on system names. Returns up to 20 results.)
This record as markdown: /tools/io-github-statico-alt-spacemolt/search-systems.md
What search_systems does on SpaceMolt
AI agents call search_systems 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 |
|---|---|---|---|
query | string | Yes | Search query - case-insensitive partial match on system names (e.g., 'sol' matches 'Sol', 'Solarian', etc.) |
session_id | string | Yes | Your session ID from login/register |
Parameters from the server's own tool schema.
Why search_systems is rated Low
The tool retrieves and returns data about game systems without modifying, creating, deleting, or executing any operations. It is a standard search/query function analogous to a database SELECT statement or API GET endpoint. The low severity reflects that searching system information in a game context poses minimal risk even if an agent uses it extensively or inappropriately.
From the tool's definition Tool performs 'Search for systems by name' with 'partial match on system names' and 'Returns up to 20 results'. This is a query operation with no side effects.
Attacks that exploit this kind of access
The rule that runs search_systems 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 search_systems, this is the rule to start with:
search_systems 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 search_systems call is checked against it from then on.
Questions about search_systems
Search for systems by name (Case-insensitive partial match on system names. Returns up to 20 results.). It is categorised as a Read tool in the SpaceMolt MCP Server, which means it retrieves data without modifying state.
search_systems accepts 2 parameters: query, session_id. Required: query, 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 search_systems: 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.
search_systems 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 search_systems 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 search_systems. 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.
search_systems 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