astroway_geo_acg_countries
Which countries the bundled city list can rank, and how many qualifying cities each has. Asking for a country with two cities and getting two results should not look like a bug. [Group: Astro-Geography] [Endpoint: GET /v1/acg/countries] [Cost: 5 credits (Tier ½)]
This record as markdown: /tools/info-astroway-astrology/astroway-geo-acg-countries.md
What astroway_geo_acg_countries does on AstroWay Astrology API (full catalogue)
AI agents call astroway_geo_acg_countries 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. |
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_countries is rated Low
Even though astroway_geo_acg_countries 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
The rule that runs astroway_geo_acg_countries 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_countries, this is the rule to start with:
astroway_geo_acg_countries is read-only, so it stays allowed. 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_countries call is checked against it from then on.
Questions about astroway_geo_acg_countries
Which countries the bundled city list can rank, and how many qualifying cities each has. Asking for a country with two cities and getting two results should not look like a bug. [Group: Astro-Geography] [Endpoint: GET /v1/acg/countries] [Cost: 5 credits (Tier ½)]. It is categorised as a Read tool in the AstroWay Astrology API (full catalogue) MCP Server, which means it retrieves data without modifying state.
astroway_geo_acg_countries accepts 2 parameters: fields, precision. 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_countries: 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_countries is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the astroway_geo_acg_countries 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_countries. 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_countries 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