astroway_webhooks_transit_trigger

Subscribe to natal-transit aspect threshold-crossings. [Group: Webhooks] [Endpoint: POST /v1/webhooks/transit-trigger] [Required: url] [Cost: 10 credits (Tier 1)]

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

High RISK CLASS

Category Execute

Parameters 31 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-webhooks-transit-trigger.md

WHAT IT DOES

What astroway_webhooks_transit_trigger does on AstroWay Astrology API (full catalogue)

AI agents invoke astroway_webhooks_transit_trigger 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
`url`	string	Yes
`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_webhooks_transit_trigger is rated High

astroway_webhooks_transit_trigger 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 signalsAccepts URL/endpoint input (url)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

astroway_webhooks_transit_trigger Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "astroway_webhooks_transit_trigger": {
      "limits": [
        {
          "counter": "astroway_webhooks_transit_trigger_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

FAQ

Questions about astroway_webhooks_transit_trigger

What does the astroway_webhooks_transit_trigger tool do? +

Subscribe to natal-transit aspect threshold-crossings. [Group: Webhooks] [Endpoint: POST /v1/webhooks/transit-trigger] [Required: url] [Cost: 10 credits (Tier 1)]. 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.

What parameters does astroway_webhooks_transit_trigger accept? +

astroway_webhooks_transit_trigger accepts 3 parameters: url, fields, precision. Required: url. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on astroway_webhooks_transit_trigger? +

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

astroway_webhooks_transit_trigger is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit astroway_webhooks_transit_trigger? +

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

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

astroway_webhooks_transit_trigger 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 → High-risk tools on this server →

Across the catalogue

qt_trigger_action on Qt → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →