근지구 천체(Near Earth Objects) 정보를 가져옵니다
AI agents call get_neo_feed to retrieve information from NASA API Desktop Extension without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool fetches and queries publicly available NASA data about near-Earth objects. It performs a read-only operation with no side effects, no code execution, no data modification, and no financial impact. The low severity reflects minimal risk even if misused—an agent can only retrieve data, not alter external systems or commit resources.
From the tool's definition Tool name 'get_neo_feed' and description '근지구 천체(Near Earth Objects) 정보를 가져옵니다' (retrieves Near Earth Objects information) indicate data retrieval with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
근지구 천체(Near Earth Objects) 정보를 가져옵니다. It is categorised as a Read tool in the NASA API Desktop Extension MCP Server, which means it retrieves data without modifying state.
Register the NASA API Desktop Extension MCP server in PolicyLayer and add a rule for get_neo_feed: 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 API Desktop Extension. Nothing to install.
get_neo_feed 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 get_neo_feed 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 get_neo_feed. 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.
get_neo_feed is provided by the NASA API Desktop Extension MCP server (seoh0711/dxt_nasa). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →