astroway_vedic_muhurat_name_change

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

Medium RISK CLASS

Category Write

Parameters 101 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-vedic-muhurat-name-change.md

WHAT IT DOES

What astroway_vedic_muhurat_name_change does on AstroWay Astrology API (full catalogue)

AI agents use astroway_vedic_muhurat_name_change 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
`topN`	integer	—
`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.
`ayanamsa`	string	—	Sidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.
`latitude`	object	—
`longitude`	object	—
`precision`	integer	—	Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
`ayanamsaId`	object	—
`timezoneOffset`	object	—	Hours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UT
`search_window_end`	string	—
`search_window_start`	string	Yes

Parameters from the server's own tool schema.

RISK

Why astroway_vedic_muhurat_name_change is rated Medium

An AI agent can call astroway_vedic_muhurat_name_change 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 (10 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

astroway_vedic_muhurat_name_change Rate-limited

astroway_vedic_muhurat_name_change 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_vedic_muhurat_name_change": {
      "limits": [
        {
          "counter": "astroway_vedic_muhurat_name_change_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_vedic_muhurat_name_change call is checked against it from then on.

FAQ

Questions about astroway_vedic_muhurat_name_change

What does the astroway_vedic_muhurat_name_change tool do? +

Auspicious-window scanner for legal or sacramental name change (uses Namkaran-derived rules with widened tithi set). Preferred nakshatras: Hasta/Chitra/Swati/Pushya/Anuradha/Revati/U.Phalguni/U.Ashadha/U.Bhadrapada. [Group: Vedic] [Endpoint: POST /v1/vedic/muhurat/name-change] [Required: search_window_start] [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.

What parameters does astroway_vedic_muhurat_name_change accept? +

astroway_vedic_muhurat_name_change accepts 10 parameters: topN, fields, ayanamsa, latitude, longitude, precision, ayanamsaId, timezoneOffset, search_window_end, search_window_start. Required: search_window_start. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on astroway_vedic_muhurat_name_change? +

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

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

Can I rate-limit astroway_vedic_muhurat_name_change? +

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

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

astroway_vedic_muhurat_name_change 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

The MCP Attack Database →

Guides

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