sky_window
This tool looks up a deterministic rules engine. Same day → same answer. Do not invent pillars or fortune claims. Call when the user asks 未来两周有什么天象 / 新月哪天 / 日食哪天 / 接下来有没有逆行 / what sky events are coming. Lists dated L1 sky marks (new/full moon, eclipse, ingress, stations). Public · local · no API ...
This record as markdown: /tools/balance-engine-mcp/sky-window.md
What sky_window does on Balance Engine
AI agents call sky_window to retrieve information from Balance Engine 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 |
|---|---|---|---|
to | string | — | End date YYYY-MM-DD. Default: from + 14 days. |
from | string | — | Start date YYYY-MM-DD. Default: today. |
locale | string | — | Reply language. zh (default) or en. |
Parameters from the server's own tool schema.
Why sky_window is rated Low
Even though sky_window only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs sky_window safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Balance Engine, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sky_window, this is the rule to start with:
sky_window 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 Balance Engine, apply this rule, and every sky_window call is checked against it from then on.
Questions about sky_window
This tool looks up a deterministic rules engine. Same day → same answer. Do not invent pillars or fortune claims. Call when the user asks 未来两周有什么天象 / 新月哪天 / 日食哪天 / 接下来有没有逆行 / what sky events are coming. Lists dated L1 sky marks (new/full moon, eclipse, ingress, stations). Public · local · no API key. Max span 45 days. Preview ≠ prediction. It is categorised as a Read tool in the Balance Engine MCP Server, which means it retrieves data without modifying state.
sky_window accepts 3 parameters: to, from, locale. The full parameter table on this page comes from the server's own tool schema.
Register the Balance Engine MCP server in PolicyLayer and add a rule for sky_window: 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 Balance Engine. Nothing to install.
sky_window 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 sky_window 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 sky_window. 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.
sky_window is provided by the Balance Engine MCP server (balance-engine-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Balance Engine, and thousands of servers like it.
This server
Across the catalogue