nasa-get-asteroids
Search for Near Earth Objects (asteroids) within a date range.
This record as markdown: /tools/io-github-derekslinz-meta-data-mcp/nasa-get-asteroids.md
What nasa-get-asteroids does on Meta Data Mcp
AI agents call nasa-get-asteroids to retrieve information from Meta Data Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why nasa-get-asteroids is rated Low
This tool performs a read-only search query against publicly available NASA data. It retrieves information about asteroids based on a date range filter but does not create, modify, delete, or execute any operations. The 'search' action and open data API context confirm this is a Read category tool. Severity is low because misuse would only result in retrieving data that is already public.
From the tool's definition Tool name 'nasa-get-asteroids' and description 'Search for Near Earth Objects (asteroids) within a date range' indicate a query operation that retrieves data from NASA's open API without modifying, executing code, or causing side effects.
Attacks that exploit this kind of access
The rule that runs nasa-get-asteroids safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Meta Data Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For nasa-get-asteroids, this is the rule to start with:
nasa-get-asteroids 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 Meta Data Mcp, apply this rule, and every nasa-get-asteroids call is checked against it from then on.
Questions about nasa-get-asteroids
Search for Near Earth Objects (asteroids) within a date range. It is categorised as a Read tool in the Meta Data Mcp MCP Server, which means it retrieves data without modifying state.
Register the Meta Data MCP server in PolicyLayer and add a rule for nasa-get-asteroids: 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 Meta Data Mcp. Nothing to install.
nasa-get-asteroids 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-get-asteroids 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-get-asteroids. 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-get-asteroids is provided by the Meta Data MCP server (pypi:meta-data-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Meta Data, and thousands of servers like it.
This server
Across the catalogue