astroway_calendar_planetary_cycles

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

High RISK CLASS

Category Execute

Parameters 64 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/info-astroway-astrology/astroway-calendar-planetary-cycles.md

WHAT IT DOES

What astroway_calendar_planetary_cycles does on AstroWay Astrology API (full catalogue)

AI agents invoke astroway_calendar_planetary_cycles to trigger actions in AstroWay Astrology API (full catalogue). What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

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.
`endDate`	string	Yes
`planet1Id`	object	Yes
`planet2Id`	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.
`startDate`	string	Yes

Parameters from the server's own tool schema.

RISK

Why astroway_calendar_planetary_cycles is rated High

astroway_calendar_planetary_cycles triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

astroway_calendar_planetary_cycles Rate-limited

astroway_calendar_planetary_cycles stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "astroway_calendar_planetary_cycles": {
      "limits": [
        {
          "counter": "astroway_calendar_planetary_cycles_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT 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_calendar_planetary_cycles call is checked against it from then on.

FAQ

Questions about astroway_calendar_planetary_cycles

What does the astroway_calendar_planetary_cycles tool do? +

Find all conjunctions between two planets within a date range, defining the start of a new synodic cycle. [Group: Calendar & Cycles] [Endpoint: POST /v1/planetary-cycles] [Required: planet1Id, planet2Id, startDate, endDate] [Cost: 100 credits (Tier 4)]. It is categorised as a Execute tool in the AstroWay Astrology API (full catalogue) MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does astroway_calendar_planetary_cycles accept? +

astroway_calendar_planetary_cycles accepts 6 parameters: fields, endDate, planet1Id, planet2Id, precision, startDate. Required: endDate, planet1Id, planet2Id, startDate. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on astroway_calendar_planetary_cycles? +

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

astroway_calendar_planetary_cycles is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit astroway_calendar_planetary_cycles? +

Yes. Add a rate_limit block to the astroway_calendar_planetary_cycles 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_calendar_planetary_cycles completely? +

Set action: deny in the PolicyLayer policy for astroway_calendar_planetary_cycles. 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_calendar_planetary_cycles? +

astroway_calendar_planetary_cycles 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 → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →