Velocity & Abuse Controls

Managed Mode reference. You do not configure these policies. They are enforced automatically to limit spam, bulk operations, and abusive velocity.

Trigger example (derived from the managed catalog)

These policies trigger when recipient/velocity signals in context exceed managed thresholds.

Example ActionKind where these policies apply: messaging.broadcast

Common required context fields: message_body, recipient_count, recipient_source

Example threshold shapes used by these policies: {"maxRecipients":50}

Example decision

json

{
  "status": "WARN",
  "decision_id": "dec_...",
  "approval_token": "appr_...",
  "reasons": [
    "Velocity limit exceeded"
  ]
}

Resolution

Apply the remediation guidance (reduce volume, add friction, or route to approval), then re-validate.

Summary	Domain	Severity	Applies to	Thresholds	Remediation
Block spammy bulk outbound messaging and unsolicited broadcasts.	abuse	BLOCK	messaging.broadcast, messaging.send	{"maxRecipients":50}	Use opt-in lists only. Add rate limits and require templates/approvals for high-volume sends.
Block outbound messages that contain secrets/credentials or sensitive internal data.	messaging	BLOCK	messaging.send, messaging.webhook	—	Redact sensitive tokens. Replace with references. Ensure destinations are allowlisted.

Legal & Responsibility Notice

Summary

Informational only

Provided for general guidance. Not legal, compliance, security, or professional advice.

You control implementation

You are responsible for policies, prompts, integrations, workflows, and regulatory requirements.

Liability limitation

To the maximum extent permitted by law, the company disclaims liability for losses arising from use of this documentation or implementations based on it.