nasa.earth.epic
Get full-disc Earth images from the DSCOVR satellite EPIC camera — daily natural color photos from Lagrange point L1, 1.5M km away (NASA EPIC)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/nasa.earth.epic.md
What nasa.earth.epic does on Apibase
AI agents call nasa.earth.epic 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 |
|---|---|---|---|
date | string | — | Date in YYYY-MM-DD format (default: most recent available). Returns DSCOVR EPIC Earth images for that date |
Parameters from the server's own tool schema.
Why nasa.earth.epic is rated Low
Retrieves publicly available satellite imagery with no side effects or data modification.
From the tool's definition Get full-disc Earth images from the DSCOVR satellite EPIC camera
Attacks that exploit this kind of access
The rule that runs nasa.earth.epic 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 nasa.earth.epic, this is the rule to start with:
nasa.earth.epic 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 nasa.earth.epic call is checked against it from then on.
Questions about nasa.earth.epic
Get full-disc Earth images from the DSCOVR satellite EPIC camera — daily natural color photos from Lagrange point L1, 1.5M km away (NASA EPIC). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
nasa.earth.epic accepts 1 parameter: date. 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 nasa.earth.epic: 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.
nasa.earth.epic 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 nasa.earth.epic 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 nasa.earth.epic. 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.
nasa.earth.epic 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