nasa.media.search
Search NASA Image and Video Library — 140K+ images, videos, and audio from missions, telescopes, and events with metadata and download links (NASA)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/nasa.media.search.md
What nasa.media.search does on Apibase
AI agents call nasa.media.search 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 |
|---|---|---|---|
q | string | Yes | Search query for NASA images and videos (e.g. "mars rover", "apollo 11", "nebula") |
page | integer | — | Page number for pagination (default 1) |
year_end | integer | — | Filter results to year <= year_end |
media_type | string | — | Filter by media type (default: all types) |
year_start | integer | — | Filter results to year >= year_start |
Parameters from the server's own tool schema.
Why nasa.media.search is rated Low
Queries public NASA media library; no side effects, creation, deletion, or financial impact.
From the tool's definition Search NASA Image and Video Library — retrieves metadata and download links
Attacks that exploit this kind of access
The rule that runs nasa.media.search 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.media.search, this is the rule to start with:
nasa.media.search 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.media.search call is checked against it from then on.
Questions about nasa.media.search
Search NASA Image and Video Library — 140K+ images, videos, and audio from missions, telescopes, and events with metadata and download links (NASA). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
nasa.media.search accepts 5 parameters: q, page, year_end, media_type, year_start. Required: q. 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.media.search: 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.media.search 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.media.search 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.media.search. 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.media.search 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