Govern what your agents do
A reviewed catalog of OPA/Rego policies for the DTwo MCP Gateway. Allow, deny, redact, or rewrite the calls AI agents make to apps like Slack, Jira, Salesforce, and HubSpot.
An AI agent connected to Slack, Jira, or your CRM can take actions with side effects you can't undo. The DTwo MCP Gateway runs an OPA/Rego policy on every tool call and decides what happens next: pass it through, deny it, redact the response, or rewrite the request before it lands.
This is the catalog of those policies — 18 of them across 4 apps and 4 bundles. Each one is small and does a single thing, so you build a posture by attaching several. If you have a problem in mind, start from a story. If you already know the policy you want, browse the full list.
Stories
- Stop AI agents from leaking secrets into Slack
Once an agent posts to Slack, an API key is in channel history and search. Catch it before the send, not after. - Keep customer PII from walking out of your CRM
An agent reading Salesforce or HubSpot pulls emails, phone numbers, and addresses into its context and your chat logs. Mask them on the way out. - Give AI agents read-only access to your CRM
For a low-risk CRM pilot, give the agent a one-way mirror: it reads every record and changes none. The read-only policies enforce that, and a query allowlist tightens it further. - Guard the CRM writes your revenue depends on
You want agents logging activities and creating records, just not closing deals or reassigning owners on their own. Gate the few writes that matter. - Wall off sensitive Jira projects from AI agents
Security, legal, and HR projects share the same Jira as your sprint board. Keep agents from reading or writing them, and redact whatever still comes back. - Slack hygiene for autonomous AI agents
Slack's OAuth scopes pick capabilities, not the channels they apply to: you can grant an agent 'post messages,' but not 'post only in #status' — one scope covers every channel at once.
Apps
- Hubspot · 6 policies
- Jira · 3 policies
- Salesforce · 4 policies
- Slack · 5 policies
Bundles
- Atlassian · 3 policies
- Crm · 10 policies
- Im Messaging · 1 policies
- Slack · 4 policies
Read it as data
Agents can read this catalog the same way people do: /llms.txt indexes it, /llms-full.txt inlines every policy, and /catalog.json serves it structured. The source of truth is the policy-store repository.