Get current weather for a city
AI agents call get-weather to retrieve information from NestJS MCP Server Module 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 for a specified city without modifying, deleting, executing code, or performing financial transactions. It is a simple data query with no destructive or irreversible consequences. The low severity reflects minimal risk even if misused by an AI agent, as the worst outcome would be repeated weather queries.
From the tool's definition Tool name 'get-weather' and description 'Get current weather for a city' indicate a data retrieval operation with no side effects. The verb 'Get' and the query-like nature of fetching current weather data confirm this is a read-only operation.
Attacks that exploit this kind of access
Get current weather for a city. It is categorised as a Read tool in the NestJS MCP Server Module MCP Server, which means it retrieves data without modifying state.
Register the NestJS MCP Server Module MCP server in PolicyLayer and add a rule for get-weather: 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 NestJS MCP Server Module. Nothing to install.
get-weather 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 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. 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 is provided by the NestJS MCP Server Module MCP server (rekog-labs/mcp-nest). 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 →