astroway_reports_relocation

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

Medium RISK CLASS

Category Write

Parameters 82 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-reports-relocation.md

WHAT IT DOES

What astroway_reports_relocation does on AstroWay Astrology API (full catalogue)

AI agents use astroway_reports_relocation 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
`chart`	object	Yes	Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and
`orbKm`	number	—
`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.
`language`	string	—
`locations`	array	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.
`categories`	array	—
`whitelabel`	object	—

Parameters from the server's own tool schema.

RISK

Why astroway_reports_relocation is rated Medium

An AI agent can call astroway_reports_relocation 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 signalsHigh parameter count (11 properties) · Bulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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

astroway_reports_relocation Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "astroway_reports_relocation": {
      "limits": [
        {
          "counter": "astroway_reports_relocation_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

FAQ

Questions about astroway_reports_relocation

What does the astroway_reports_relocation tool do? +

Compare up to five places for one birth chart as a multi-page A4 PDF (default) or live HTML (add ?format=html). Per place: the relocated ascendant and midheaven with the signed shift from birth, which planets changed house (the substantive difference, diffed rather than left as two tables), every astrocartography line running within 300 km with its interpretation text, and supportive/challenging scores across the 19 life categories. With more than one place a side-by-side comparison leads the document. [Group: Reports] [Endpoint: POST /v1/reports/relocation] [Required: chart, locations] [Cost: 5,000 credits (Tier 7)] ⚠️ Premium — ~50% of free monthly budget. Confirm with user before invoking. 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.

What parameters does astroway_reports_relocation accept? +

astroway_reports_relocation accepts 8 parameters: chart, orbKm, fields, language, locations, precision, categories, whitelabel. Required: chart, locations. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on astroway_reports_relocation? +

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

astroway_reports_relocation is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit astroway_reports_relocation? +

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

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

astroway_reports_relocation 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

combine_reports on Android Forensics ADB MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →