astroway_stream_planetary_hour_changes

Current planetary hour + next 24. [Group: Real-time Streaming] [Endpoint: POST /v1/stream/planetary-hour-changes] [Required: latitude, longitude] [Cost: 10 credits (Tier 1)]

SERVERAstroWay Astrology API (full catalogue) SOURCEhttps://mcp.astroway.info/mcp

Low RISK CLASS

Category Read

Parameters 52 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/info-astroway-astrology/astroway-stream-planetary-hour-changes.md

WHAT IT DOES

What astroway_stream_planetary_hour_changes does on AstroWay Astrology API (full catalogue)

AI agents call astroway_stream_planetary_hour_changes to retrieve information from AstroWay Astrology API (full catalogue) 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
`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
`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.
`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.

RISK

Why astroway_stream_planetary_hour_changes is rated Low

Even though astroway_stream_planetary_hour_changes 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

RECOMMENDED RULE

The rule that runs astroway_stream_planetary_hour_changes 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_stream_planetary_hour_changes, this is the rule to start with:

astroway_stream_planetary_hour_changes Allowed

astroway_stream_planetary_hour_changes is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "astroway_stream_planetary_hour_changes": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect AstroWay Astrology API (full catalogue), apply this rule, and every astroway_stream_planetary_hour_changes call is checked against it from then on.

FAQ

Questions about astroway_stream_planetary_hour_changes

What does the astroway_stream_planetary_hour_changes tool do? +

Current planetary hour + next 24. [Group: Real-time Streaming] [Endpoint: POST /v1/stream/planetary-hour-changes] [Required: latitude, longitude] [Cost: 10 credits (Tier 1)]. It is categorised as a Read tool in the AstroWay Astrology API (full catalogue) MCP Server, which means it retrieves data without modifying state.

What parameters does astroway_stream_planetary_hour_changes accept? +

astroway_stream_planetary_hour_changes accepts 5 parameters: fields, latitude, longitude, precision, timezoneOffset. Required: latitude, longitude. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on astroway_stream_planetary_hour_changes? +

Register the AstroWay Astrology API (full catalogue) MCP server in PolicyLayer and add a rule for astroway_stream_planetary_hour_changes: 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.

What risk level is astroway_stream_planetary_hour_changes? +

astroway_stream_planetary_hour_changes is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit astroway_stream_planetary_hour_changes? +

Yes. Add a rate_limit block to the astroway_stream_planetary_hour_changes 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.

How do I block astroway_stream_planetary_hour_changes completely? +

Set action: deny in the PolicyLayer policy for astroway_stream_planetary_hour_changes. 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.

What MCP server provides astroway_stream_planetary_hour_changes? +

astroway_stream_planetary_hour_changes 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.

KEEP EXPLORING

More on AstroWay Astrology API (full catalogue), and thousands of servers like it.

This server

All 799 AstroWay Astrology API (full catalogue) tools →

Across the catalogue

review_changes on MCP Server PR Pilot → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →