Low Risk

get_apod_date_range

Get APOD entries for a date range.

How to control get_apod_date_range ↓

What get_apod_date_range does on Nasa

AI agents call get_apod_date_range to retrieve information from Nasa without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_apod_date_range needs a policy

This tool retrieves or queries APOD (Astronomy Picture of the Day) data for a specified date range. It has no side effects, does not modify data, execute code, delete records, or move money. The operation is a straightforward data retrieval from a public API. Misuse by an AI agent would be limited to excessive API calls or information gathering, which poses minimal security risk.

From the tool's definition Tool name 'get_apod_date_range' and description 'Get APOD entries for a date range' indicate a retrieval operation. APOD (Astronomy Picture of the Day) is a public NASA dataset.

Documented attack patterns abuse exactly the kind of access get_apod_date_range gives an agent:

How to control get_apod_date_range

PolicyLayer is an MCP gateway — it sits between your AI agents and Nasa, and nothing reaches the server without passing your rules. This is the rule we recommend for get_apod_date_range:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_apod_date_range": {}
  }
}

get_apod_date_range is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Nasa — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_apod_date_range

What does the get_apod_date_range tool do? +

Get APOD entries for a date range. It is categorised as a Read tool in the Nasa MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_apod_date_range? +

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

What risk level is get_apod_date_range? +

get_apod_date_range is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_apod_date_range? +

Yes. Add a rate_limit block to the get_apod_date_range 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 get_apod_date_range completely? +

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

get_apod_date_range is provided by the Nasa MCP server (jezweb/nasa-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Nasa tool call.

Start from Nasa, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

11 Nasa tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.