get_weather_by_position
AI agents call get_weather_by_position 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 retrieves weather information based on position input, which is a read-only query operation with no side effects. It aligns with the server's astronomy/stargazing use case. The confidence is moderate (0.7) rather than high because the tool description is empty, leaving some ambiguity, but the name and context strongly suggest simple data retrieval.
From the tool's definition Tool name 'get_weather_by_position' indicates retrieval of weather data for a given geographic location. The server's purpose is to calculate and provide information about celestial objects and stargazing conditions.
Attacks that exploit this kind of access
get_weather_by_position. 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_weather_by_position: 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_weather_by_position 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_weather_by_position 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_weather_by_position. 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_weather_by_position 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 →