Low Risk

iss_now

Current latitude / longitude of the International Space Station.

Part of the Open Notify server.

iss_now is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE OPEN NOTIFY →

Free to start. No card required.

AI agents call iss_now to retrieve information from Open Notify without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though iss_now only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

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

See the full Open Notify policy for all 22 tools.

Get this rule live on your own Open Notify server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY OPEN NOTIFY →

View all 22 tools →

These attack patterns abuse exactly the kind of access iss_now gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so iss_now only ever does what you allow.

SECURE OPEN NOTIFY →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the iss_now tool do? +

Current latitude / longitude of the International Space Station.. It is categorised as a Read tool in the Open Notify MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on iss_now? +

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

What risk level is iss_now? +

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

Can I rate-limit iss_now? +

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

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

iss_now is provided by the Open Notify MCP server (https://gateway.pipeworx.io/open-notify/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Open Notify tool call.

Deterministic rules across all 22 Open Notify tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.