Get light pollution data for a specific area.
AI agents call light_pollution_map to retrieve information from Mcp Stargazing without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns light pollution information for a geographic location. It is a read-only data retrieval operation with no capability to modify, delete, execute code, or trigger external operations. The tool fits squarely within the 'Read' category as it merely retrieves or queries data without side effects. Low severity due to the benign nature of the data being accessed and retrieved.
From the tool's definition Tool retrieves light pollution data for a specific area. Description indicates data retrieval with no modification, creation, deletion, or side effects: 'Get light pollution data'
Attacks that exploit this kind of access
Get light pollution data for a specific area. It is categorised as a Read tool in the Mcp Stargazing MCP Server, which means it retrieves data without modifying state.
Register the Mcp Stargazing MCP server in PolicyLayer and add a rule for light_pollution_map: 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 Mcp Stargazing. Nothing to install.
light_pollution_map 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 light_pollution_map 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 light_pollution_map. 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.
light_pollution_map is provided by the Mcp Stargazing MCP server (stargazer1995/mcp-stargazing). 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 →