astroway_vedic_compatibility_dashakoota

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

Critical RISK CLASS

Category Destructive

Parameters 42 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/info-astroway-astrology/astroway-vedic-compatibility-dashakoota.md

WHAT IT DOES

What astroway_vedic_compatibility_dashakoota does on AstroWay Astrology API (full catalogue)

AI agents call astroway_vedic_compatibility_dashakoota to permanently remove resources in AstroWay Astrology API (full catalogue), typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Parameter	Type	Required	Description
`chart1`	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
`chart2`	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
`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.

RISK

Why astroway_vedic_compatibility_dashakoota is rated Critical

An AI agent that decides to call astroway_vedic_compatibility_dashakoota doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from AstroWay Astrology API (full catalogue) is gone. There is no undo for destructive operations.

Risk signalsHigh parameter count (30 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

astroway_vedic_compatibility_dashakoota Hidden

astroway_vedic_compatibility_dashakoota is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "astroway_vedic_compatibility_dashakoota"
  ]
}

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

FAQ

Questions about astroway_vedic_compatibility_dashakoota

What does the astroway_vedic_compatibility_dashakoota tool do? +

Extended matchmaking adding Mahendra(2) + Vedha(1) on top of Ashtakoot 36 = 39 max. Mahendra: birth-star count 4/7/10/13/16/19/22/25 → 2pt; else 0. Vedha: 13 canonical mutually-obstructing nakshatra pairs → 0pt blocked, 1pt clear. [Group: Vedic] [Endpoint: POST /v1/vedic/compatibility/dashakoota] [Required: chart1, chart2] [Cost: 50 credits (Tier 3)]. It is categorised as a Destructive tool in the AstroWay Astrology API (full catalogue) MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

What parameters does astroway_vedic_compatibility_dashakoota accept? +

astroway_vedic_compatibility_dashakoota accepts 4 parameters: chart1, chart2, fields, precision. Required: chart1, chart2. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on astroway_vedic_compatibility_dashakoota? +

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

astroway_vedic_compatibility_dashakoota is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit astroway_vedic_compatibility_dashakoota? +

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

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

astroway_vedic_compatibility_dashakoota 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 → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →