jpl.asteroids.sentry
Get asteroid impact risk assessments from the Sentry monitoring system — impact probability, Palermo/Torino scale, size estimates (NASA JPL)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/jpl.asteroids.sentry.md
What jpl.asteroids.sentry does on Apibase
AI agents call jpl.asteroids.sentry 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 |
|---|---|---|---|
des | string | — | Asteroid designation to check specific object (e.g. "99942" for Apophis). Omit for full list |
h_max | number | — | Maximum absolute magnitude H — filter for larger objects |
ip_min | number | — | Minimum impact probability (e.g. 1e-7) |
ps_min | number | — | Minimum Palermo Scale value (e.g. -3). Higher = more concerning |
Parameters from the server's own tool schema.
Why jpl.asteroids.sentry is rated Low
Read-only retrieval of asteroid risk data from NASA JPL Sentry system.
From the tool's definition Get asteroid impact risk assessments... impact probability, size estimates
Attacks that exploit this kind of access
The rule that runs jpl.asteroids.sentry 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 jpl.asteroids.sentry, this is the rule to start with:
jpl.asteroids.sentry 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 jpl.asteroids.sentry call is checked against it from then on.
Questions about jpl.asteroids.sentry
Get asteroid impact risk assessments from the Sentry monitoring system — impact probability, Palermo/Torino scale, size estimates (NASA JPL). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
jpl.asteroids.sentry accepts 4 parameters: des, h_max, ip_min, ps_min. 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 jpl.asteroids.sentry: 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.
jpl.asteroids.sentry 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 jpl.asteroids.sentry 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 jpl.asteroids.sentry. 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.
jpl.asteroids.sentry 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