astroway_calendar_planetary_hours
Chaldean planetary hours for a date and place: 12 from sunrise to sunset and 12 from sunset to sunrise, so an hour is rarely 60 minutes. startHour and endHour are decimal local hours. Send atLocalHour (decimal local time, e.g. 15.2 for 15:12) to have the hour containing it marked isCurrent; witho...
This record as markdown: /tools/info-astroway-astrology/astroway-calendar-planetary-hours.md
What astroway_calendar_planetary_hours does on AstroWay Astrology API (full catalogue)
AI agents use astroway_calendar_planetary_hours to create or update resources in AstroWay Astrology API (full catalogue), usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AstroWay Astrology API (full catalogue) environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
date | string | Yes | |
fields | string | — | Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response. |
latitude | object | Yes | |
timezone | string | — | IANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and t |
longitude | object | Yes | |
precision | integer | — | Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn. |
atLocalHour | number | — | Local time of day in decimal hours, e.g. 15.2 for 15:12. When sent, the hour containing it carries isCurrent: true and every other hour carries false. When omit |
timezoneOffset | object | — | Hours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UT |
Parameters from the server's own tool schema.
Why astroway_calendar_planetary_hours is rated Medium
An AI agent can call astroway_calendar_planetary_hours faster than any human can review: one bad instruction and it creates or modifies resources in AstroWay Astrology API (full catalogue) by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs astroway_calendar_planetary_hours safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AstroWay Astrology API (full catalogue), and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For astroway_calendar_planetary_hours, this is the rule to start with:
astroway_calendar_planetary_hours stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect AstroWay Astrology API (full catalogue), apply this rule, and every astroway_calendar_planetary_hours call is checked against it from then on.
Questions about astroway_calendar_planetary_hours
Chaldean planetary hours for a date and place: 12 from sunrise to sunset and 12 from sunset to sunrise, so an hour is rarely 60 minutes. startHour and endHour are decimal local hours. Send atLocalHour (decimal local time, e.g. 15.2 for 15:12) to have the hour containing it marked isCurrent; without it no hour carries the field, because the answer is cacheable and a flag from the server clock would be stale by the time it renders. [Group: Calendar & Cycles] [Endpoint: POST /v1/planetary-hours] [Required: date, latitude, longitude] [Cost: 10 credits (Tier 1)]. It is categorised as a Write tool in the AstroWay Astrology API (full catalogue) MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
astroway_calendar_planetary_hours accepts 8 parameters: date, fields, latitude, timezone, longitude, precision, atLocalHour, timezoneOffset. Required: date, latitude, longitude. The full parameter table on this page comes from the server's own tool schema.
Register the AstroWay Astrology API (full catalogue) MCP server in PolicyLayer and add a rule for astroway_calendar_planetary_hours: 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 AstroWay Astrology API (full catalogue). Nothing to install.
astroway_calendar_planetary_hours is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the astroway_calendar_planetary_hours 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 astroway_calendar_planetary_hours. 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.
astroway_calendar_planetary_hours is provided by the AstroWay Astrology API (full catalogue) MCP server (https://mcp.astroway.info/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AstroWay Astrology API (full catalogue), and thousands of servers like it.
Across the catalogue