MCP Resources
The Guidelines resource — Meta WhatsApp policy reminders the agent reads before proposing actions.
Resources are read-only documents the MCP server publishes for the agent to consult. Qyvo ships one today: the Guidelines resource.
guidelines
A concise summary of Meta's WhatsApp Business Platform policy as it applies to your workspace. The agent should consult it before composing a campaign or proposing a free-form message. Topics covered:
- The 24h customer service window — when free-form text is allowed, when it isn't.
- Opt-in requirements — what counts as consent, how to record it, what happens if you can't prove it during a Meta audit.
- Template categories —
UTILITY,MARKETING,AUTHENTICATION, what each is for, and which incurs higher Meta fees. - Forbidden content — the categories Meta will reject (gambling, adult, alcohol in restricted markets, etc.).
- Frequency caps — Meta's evolving guidance on per-day messaging tier limits.
The agent receives the full text the first time it runs a Qyvo session, then references it before destructive sends — Claude in particular will cite the relevant clause when refusing or warning.
Why a resource and not a tool?
Resources are passive: the agent reads them as context, doesn't invoke them. Encoding policy as a resource makes refusals consistent without burning tokens on a check_policy round-trip. It also keeps the MCP server's tool surface focused on actions.
Updating the resource
The resource is regenerated server-side whenever Meta updates its policy. New rules show up automatically — no client config change needed.