get_constellation
AI agents call get_constellation 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 almost certainly retrieves constellation information for stargazing purposes, consistent with the read-only nature of all sibling tools on this astronomy calculation server. The empty description prevents higher confidence, but the naming pattern and server context strongly indicate a data retrieval operation with no side effects or external modifications.
From the tool's definition Tool name 'get_constellation' combined with server purpose of calculating celestial object positions and properties. Sibling tools are all query/retrieval operations (get_celestial_pos, get_moon_info, get_nightly_forecast, etc.).
Attacks that exploit this kind of access
get_constellation. 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 get_constellation: 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.
get_constellation 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_constellation 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_constellation. 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_constellation 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 →