astroway_geo_acg_best_places
Rank cities against the astrocartography lines of a chart for one of the 19 life categories. Distance to a line is computed from the body hour angle and altitude rather than against a discretised polyline, so it is exact: the distance to a horizon line IS the altitude in degrees of arc, and a mer...
This record as markdown: /tools/info-astroway-astrology/astroway-geo-acg-best-places.md
What astroway_geo_acg_best_places does on AstroWay Astrology API (full catalogue)
AI agents use astroway_geo_acg_best_places 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 plus a life category. Birth coordinates are optional and unused for the ranking: astrocartography lines are a property of the birth moment, not of th |
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_acg_best_places is rated Medium
An AI agent can call astroway_geo_acg_best_places 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) · Bulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs astroway_geo_acg_best_places 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_acg_best_places, this is the rule to start with:
astroway_geo_acg_best_places 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_acg_best_places call is checked against it from then on.
Questions about astroway_geo_acg_best_places
Rank cities against the astrocartography lines of a chart for one of the 19 life categories. Distance to a line is computed from the body hour angle and altitude rather than against a discretised polyline, so it is exact: the distance to a horizon line IS the altitude in degrees of arc, and a meridian line offset is the hour angle times cos(latitude). Supportive and challenging totals are returned separately with every contributing line and its distance, so a strong-but-turbulent city is distinguishable from an average one. Bundled GeoNames set of 34,028 places above 15,000 people. [Group: Astro-Geography] [Endpoint: POST /v1/acg/best-places] [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_acg_best_places 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_acg_best_places: 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_acg_best_places 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_acg_best_places 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_acg_best_places. 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_acg_best_places 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