nasa.asteroids.feed
Get near-Earth asteroid close approaches for a date range — size estimates, hazard classification, velocity, miss distance (NASA NeoWs)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/nasa.asteroids.feed.md
What nasa.asteroids.feed does on Apibase
AI agents call nasa.asteroids.feed 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 |
|---|---|---|---|
end_date | string | — | End date in YYYY-MM-DD format (default: start_date + 7 days) |
start_date | string | Yes | Start date in YYYY-MM-DD format for asteroid feed (max 7-day span) |
Parameters from the server's own tool schema.
Why nasa.asteroids.feed is rated Low
Tool retrieves asteroid data with no side effects, modifications, or operations triggered.
From the tool's definition Get near-Earth asteroid close approaches, size estimates, hazard classification, velocity, miss distance
Attacks that exploit this kind of access
The rule that runs nasa.asteroids.feed 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.asteroids.feed, this is the rule to start with:
nasa.asteroids.feed 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.asteroids.feed call is checked against it from then on.
Questions about nasa.asteroids.feed
Get near-Earth asteroid close approaches for a date range — size estimates, hazard classification, velocity, miss distance (NASA NeoWs). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
nasa.asteroids.feed accepts 2 parameters: end_date, start_date. Required: start_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.asteroids.feed: 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.asteroids.feed 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.asteroids.feed 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.asteroids.feed. 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.asteroids.feed 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