This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/tomorrow-realtime.md
What tomorrow_realtime does on UnClick
AI agents call tomorrow_realtime to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
units | string | — | |
api_key | string | — | |
location | string | Yes | lat,lon or place name |
Parameters from the server's own tool schema.
Why tomorrow_realtime is rated Low
This tool retrieves real-time weather data from an external API. It performs a query operation with no side effects, no code execution, no data modification, and no financial implications. It is purely informational and read-only, making it the lowest risk category.
From the tool's definition Tool name 'tomorrow_realtime' and description 'Get realtime weather from Tomorrow.io' indicate data retrieval with no modification, deletion, or execution capabilities.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs tomorrow_realtime safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For tomorrow_realtime, this is the rule to start with:
tomorrow_realtime is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every tomorrow_realtime call is checked against it from then on.
Questions about tomorrow_realtime
Get realtime weather from Tomorrow.io. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
tomorrow_realtime accepts 3 parameters: units, api_key, location. Required: location. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for tomorrow_realtime: 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 UnClick. Nothing to install.
tomorrow_realtime 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 tomorrow_realtime 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 tomorrow_realtime. 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.
tomorrow_realtime is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue