space.swpc.solar_wind
Real-time solar wind speed (km/s), proton density (per cm³), and temperature (K) from the ACE/DSCOVR L1 monitors. Returns the latest reading plus the last N 1-minute observations. Source: NOAA SWPC RTSW (NODD public domain)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/space.swpc.solar-wind.md
What space.swpc.solar_wind does on Apibase
AI agents call space.swpc.solar_wind to retrieve information from Apibase 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 |
|---|---|---|---|
points | integer | — | Number of recent 1-minute solar-wind readings to return alongside the latest reading (default 20, max 60). Each reading includes proton speed (km/s), density (p |
Parameters from the server's own tool schema.
Why space.swpc.solar_wind is rated Low
Retrieves real-time public scientific data without side effects or modifications.
From the tool's definition Real-time solar wind speed, proton density, temperature from ACE/DSCOVR. Returns latest reading plus observations.
Attacks that exploit this kind of access
The rule that runs space.swpc.solar_wind safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For space.swpc.solar_wind, this is the rule to start with:
space.swpc.solar_wind 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 Apibase, apply this rule, and every space.swpc.solar_wind call is checked against it from then on.
Questions about space.swpc.solar_wind
Real-time solar wind speed (km/s), proton density (per cm³), and temperature (K) from the ACE/DSCOVR L1 monitors. Returns the latest reading plus the last N 1-minute observations. Source: NOAA SWPC RTSW (NODD public domain). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
space.swpc.solar_wind accepts 1 parameter: points. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for space.swpc.solar_wind: 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 Apibase. Nothing to install.
space.swpc.solar_wind 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 space.swpc.solar_wind 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 space.swpc.solar_wind. 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.
space.swpc.solar_wind is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue