tomorrow_history
Get historical weather data from Tomorrow.io.
This record as markdown: /tools/creativelead-unclick/tomorrow-history.md
What tomorrow_history does on UnClick
AI agents call tomorrow_history 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 |
|---|---|---|---|
api_key | string | — | |
endTime | string | — | |
location | string | — | |
startTime | string | — |
Parameters from the server's own tool schema.
Why tomorrow_history is rated Low
This tool retrieves past weather information from an external service (Tomorrow.io). It is a pure read operation that queries existing data without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal - an agent could only retrieve weather history data, which poses no security or operational risk.
From the tool's definition Tool description states 'Get historical weather data from Tomorrow.io' - the verb 'Get' and 'historical' indicate data retrieval with no modification or side effects.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs tomorrow_history 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_history, this is the rule to start with:
tomorrow_history 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_history call is checked against it from then on.
Questions about tomorrow_history
Get historical weather data from Tomorrow.io. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
tomorrow_history accepts 4 parameters: api_key, endTime, location, startTime. 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_history: 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_history 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_history 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_history. 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_history is provided by the UnClick MCP server (creativelead/unclick). 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