astroway_geo_parans_star
Latitudes where a fixed star and a planet are angular at the same moment, which is how Brady tabulates a paran: not a place, a latitude. Twelve event pairs per star and planet (rise, set, culminate, anticulminate, minus meridian against meridian, which is a shared right ascension rather than a pa...
This record as markdown: /tools/info-astroway-astrology/astroway-geo-parans-star.md
What astroway_geo_parans_star does on AstroWay Astrology API (full catalogue)
AI agents use astroway_geo_parans_star 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 |
|---|---|---|---|
body | object | Yes | Birth data for star-planet parans. Coordinates are not used: a paran is a latitude, and which latitudes exist depends on the moment, not on where the native was |
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. |
precision | integer | — | Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn. |
Parameters from the server's own tool schema.
Why astroway_geo_parans_star is rated Medium
An AI agent can call astroway_geo_parans_star 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.
Risk signalsAccepts raw HTML/template content (body)
Attacks that exploit this kind of access
The rule that runs astroway_geo_parans_star 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_geo_parans_star, this is the rule to start with:
astroway_geo_parans_star 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_geo_parans_star call is checked against it from then on.
Questions about astroway_geo_parans_star
Latitudes where a fixed star and a planet are angular at the same moment, which is how Brady tabulates a paran: not a place, a latitude. Twelve event pairs per star and planet (rise, set, culminate, anticulminate, minus meridian against meridian, which is a shared right ascension rather than a paran). Each row carries the houses of the technique in plain form: which body does what, the latitude, and the meridian where it happens at this chart moment. Solved on hour angles rather than by intersecting map polylines, so the latitude is exact rather than quantised to the polyline step. [Group: Astro-Geography] [Endpoint: POST /v1/parans/star] [Cost: 50 credits (Tier 3)]. 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_geo_parans_star accepts 3 parameters: body, fields, precision. Required: body. 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_geo_parans_star: 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_geo_parans_star 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_geo_parans_star 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_geo_parans_star. 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_geo_parans_star 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