This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/spacex-rockets.md
What spacex_rockets does on UnClick
AI agents call spacex_rockets to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why spacex_rockets is rated Low
This tool performs a read-only operation that lists and retrieves information about SpaceX rockets. There are no side effects, data modifications, code execution, deletions, or financial implications. It is a simple data lookup/query operation against likely public SpaceX information, making it a Read category tool with low severity.
From the tool's definition Tool name 'spacex_rockets' and description 'List all SpaceX rockets with specifications' indicate a retrieval operation that queries public data about SpaceX rockets.
Attacks that exploit this kind of access
The rule that runs spacex_rockets safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For spacex_rockets, this is the rule to start with:
spacex_rockets 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 UnClick, apply this rule, and every spacex_rockets call is checked against it from then on.
Questions about spacex_rockets
List all SpaceX rockets with specifications. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
Register the UnClick MCP server in PolicyLayer and add a rule for spacex_rockets: 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 UnClick. Nothing to install.
spacex_rockets 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 spacex_rockets 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 spacex_rockets. 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.
spacex_rockets is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue