New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

asteroid_close_approaches

skypeek: List asteroid and comet close approaches to Earth. For space weather use get_space_weather. Returns near-Earth object close approaches to Earth in the next 1-30 days within a miss distance (default 0.05 au, about 19.5 lunar distances): designation, approach time, nominal distance with it...

SERVERTanod SOURCEhttps://tanod.dev/mcp
Medium RISK CLASS
Category Write
Parameters 20 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dev-tanod-tanod/asteroid-close-approaches.md

What asteroid_close_approaches does on Tanod

AI agents use asteroid_close_approaches to create or update resources in Tanod, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tanod environment.

ParameterTypeRequiredDescription
days integer — Look-ahead window in days (1-30).
dist_max_au number — Largest nominal miss distance in au (0.0001-0.2; 0.05 au is about 19.5 lunar distances).

Parameters from the server's own tool schema.

Why asteroid_close_approaches is rated Medium

An AI agent can call asteroid_close_approaches faster than any human can review: one bad instruction and it creates or modifies resources in Tanod by the hundred, each call as confident as the last.

Questions about asteroid_close_approaches

What does the asteroid_close_approaches tool do? +

skypeek: List asteroid and comet close approaches to Earth. For space weather use get_space_weather. Returns near-Earth object close approaches to Earth in the next 1-30 days within a miss distance (default 0.05 au, about 19.5 lunar distances): designation, approach time, nominal distance with its 3-sigma range, relative velocity, absolute magnitude and diameter (published or a rough range). Data: NASA/JPL Solar System Dynamics close-approach API (US Government work); no endorsement by NASA or JPL is implied. At most 100 approaches per answer. Not an impact-risk assessment. Cached up to an hour. An upstream outage is a 503 upstream_unavailable (not charged). Typically under 1 s. Price: USD 0.001. Free: 5 skypeek calls per IP per UTC day. Docs: https://tanod.dev/learn/asteroid-close-approach-api.html. It is categorised as a Write tool in the Tanod MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does asteroid_close_approaches accept? +

asteroid_close_approaches accepts 2 parameters: days, dist_max_au. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on asteroid_close_approaches? +

Register the Tanod MCP server in PolicyLayer and add a rule for asteroid_close_approaches: 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 Tanod. Nothing to install.

What risk level is asteroid_close_approaches? +

asteroid_close_approaches is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit asteroid_close_approaches? +

Yes. Add a rate_limit block to the asteroid_close_approaches 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.

How do I block asteroid_close_approaches completely? +

Set action: deny in the PolicyLayer policy for asteroid_close_approaches. 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.

What MCP server provides asteroid_close_approaches? +

asteroid_close_approaches is provided by the Tanod MCP server (https://tanod.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Tanod, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Tanod's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.