astroway_vedic_panchang_full
Complete daily Panchang: Tithi, Vara, Karana, Yoga, Nakshatra + Choghadia + Rahu Kaal + Yamaganda + Gulika + Abhijit Muhurat. Single call. Tithi, karana, yoga and nakshatra carry endsAt (local ISO time with offset); sunNakshatra, moonrise and moonset (first after sunrise, disc centre on the horiz...
This record as markdown: /tools/info-astroway-astrology/astroway-vedic-panchang-full.md
What astroway_vedic_panchang_full does on AstroWay Astrology API (full catalogue)
AI agents invoke astroway_vedic_panchang_full to trigger actions in AstroWay Astrology API (full catalogue). What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
at | string | — | moment (default): tithi, nakshatra, yoga and karana at date + time. sunrise: at local sunrise of that date, as a printed panchang gives them; time may be omitte |
city | string | — | |
date | string | Yes | |
name | string | — | |
time | string | — | |
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 | number | Yes | |
timezone | string | — | IANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and t |
cosmogram | boolean | — | |
longitude | number | 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. |
Parameters from the server's own tool schema.
Why astroway_vedic_panchang_full is rated High
astroway_vedic_panchang_full triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Risk signalsHigh parameter count (16 properties)
Attacks that exploit this kind of access
The rule that runs astroway_vedic_panchang_full 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_panchang_full, this is the rule to start with:
astroway_vedic_panchang_full stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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_vedic_panchang_full call is checked against it from then on.
Questions about astroway_vedic_panchang_full
Complete daily Panchang: Tithi, Vara, Karana, Yoga, Nakshatra + Choghadia + Rahu Kaal + Yamaganda + Gulika + Abhijit Muhurat. Single call. Tithi, karana, yoga and nakshatra carry endsAt (local ISO time with offset); sunNakshatra, moonrise and moonset (first after sunrise, disc centre on the horizon as panchangs count it; null when the Moon does not rise or set within 30 hours). muhurtas: Brahma Muhurta, Pratah and Sayahna Sandhya, Vijaya, Godhuli, Nishita, durMuhurtam, amritKalam and varjyam (lists), each { start, end } in local ISO time. [Group: Vedic] [Endpoint: POST /v1/vedic/panchang/full] [Required: date, latitude, longitude] [Cost: 20 credits (Tier 2)]. It is categorised as a Execute tool in the AstroWay Astrology API (full catalogue) MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
astroway_vedic_panchang_full accepts 12 parameters: at, city, date, name, time, fields, ayanamsa, latitude, timezone, cosmogram, longitude, precision. Required: date, latitude, longitude. 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_vedic_panchang_full: 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_vedic_panchang_full is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the astroway_vedic_panchang_full 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_vedic_panchang_full. 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_vedic_panchang_full 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.
This server
Across the catalogue