# cdp_list_output_connector_defs

List available output connector definitions

Agent View of the PolicyLayer registry record for `cdp_list_output_connector_defs`. HTML page: https://policylayer.com/tools/atharva-joshi77-cdp-mcp/cdp-list-output-connector-defs

## Facts

- Tool: `cdp_list_output_connector_defs`
- Server: CDP MCP Server (`atharva-joshi77/cdp-mcp`) — https://policylayer.com/tools/atharva-joshi77-cdp-mcp.md
- Homepage: https://github.com/atharva-joshi77/cdp-mcp
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "cdp_list_output_connector_defs",
    "arguments": {}
  }
}
```

## Why cdp_list_output_connector_defs is rated Low

This tool retrieves and lists existing connector definitions from the CDP platform. It performs a query operation with no side effects, no data modification, no code execution, and no destructive actions. The only security concern is potential information disclosure of connector metadata, which is generally low severity in administrative contexts. Therefore, it is classified as Read with low severity.

From the tool's own definition: "Tool name 'cdp_list_output_connector_defs' with description 'List available output connector definitions' indicates a retrieval/query operation that enumerates configuration options without modifying or executing anything."

## Use case

AI agents call cdp_list_output_connector_defs to retrieve information from CDP MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches CDP MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "cdp_list_output_connector_defs": {}
  }
}
```

## Other tools on CDP MCP Server (287)

- `cdp_cache_delete_by_group` — Destructive — https://policylayer.com/tools/atharva-joshi77-cdp-mcp/cdp-cache-delete-by-group.md
- `cdp_cache_delete_by_id` — Destructive — https://policylayer.com/tools/atharva-joshi77-cdp-mcp/cdp-cache-delete-by-id.md
- `cdp_cache_delete_by_key` — Destructive — https://policylayer.com/tools/atharva-joshi77-cdp-mcp/cdp-cache-delete-by-key.md
- `cdp_deactivate_provision_instance` — Destructive — https://policylayer.com/tools/atharva-joshi77-cdp-mcp/cdp-deactivate-provision-instance.md
- `cdp_delete_a360_rule` — Destructive — https://policylayer.com/tools/atharva-joshi77-cdp-mcp/cdp-delete-a360-rule.md
- `cdp_delete_alert` — Destructive — https://policylayer.com/tools/atharva-joshi77-cdp-mcp/cdp-delete-alert.md
- `cdp_delete_alert_def` — Destructive — https://policylayer.com/tools/atharva-joshi77-cdp-mcp/cdp-delete-alert-def.md
- `cdp_delete_audience_def` — Destructive — https://policylayer.com/tools/atharva-joshi77-cdp-mcp/cdp-delete-audience-def.md
- `cdp_delete_campaign` — Destructive — https://policylayer.com/tools/atharva-joshi77-cdp-mcp/cdp-delete-campaign.md
- `cdp_delete_client` — Destructive — https://policylayer.com/tools/atharva-joshi77-cdp-mcp/cdp-delete-client.md
- `cdp_delete_column_validator` — Destructive — https://policylayer.com/tools/atharva-joshi77-cdp-mcp/cdp-delete-column-validator.md
- `cdp_delete_connector` — Destructive — https://policylayer.com/tools/atharva-joshi77-cdp-mcp/cdp-delete-connector.md
- `cdp_delete_connector_template` — Destructive — https://policylayer.com/tools/atharva-joshi77-cdp-mcp/cdp-delete-connector-template.md
- `cdp_delete_cubic_set_def` — Destructive — https://policylayer.com/tools/atharva-joshi77-cdp-mcp/cdp-delete-cubic-set-def.md
- `cdp_delete_dashboard` — Destructive — https://policylayer.com/tools/atharva-joshi77-cdp-mcp/cdp-delete-dashboard.md
- `cdp_delete_data_erasure_request` — Destructive — https://policylayer.com/tools/atharva-joshi77-cdp-mcp/cdp-delete-data-erasure-request.md
- `cdp_delete_data_export` — Destructive — https://policylayer.com/tools/atharva-joshi77-cdp-mcp/cdp-delete-data-export.md
- `cdp_delete_dispatch` — Destructive — https://policylayer.com/tools/atharva-joshi77-cdp-mcp/cdp-delete-dispatch.md
- `cdp_delete_emailable_page` — Destructive — https://policylayer.com/tools/atharva-joshi77-cdp-mcp/cdp-delete-emailable-page.md
- `cdp_delete_execution_bucket` — Destructive — https://policylayer.com/tools/atharva-joshi77-cdp-mcp/cdp-delete-execution-bucket.md
- `cdp_delete_execution_summary_group` — Destructive — https://policylayer.com/tools/atharva-joshi77-cdp-mcp/cdp-delete-execution-summary-group.md
- `cdp_delete_mapping_template` — Destructive — https://policylayer.com/tools/atharva-joshi77-cdp-mcp/cdp-delete-mapping-template.md
- `cdp_delete_message_def` — Destructive — https://policylayer.com/tools/atharva-joshi77-cdp-mcp/cdp-delete-message-def.md
- `cdp_delete_output_connector` — Destructive — https://policylayer.com/tools/atharva-joshi77-cdp-mcp/cdp-delete-output-connector.md
- `cdp_delete_output_connector_def` — Destructive — https://policylayer.com/tools/atharva-joshi77-cdp-mcp/cdp-delete-output-connector-def.md
- `cdp_delete_prediction` — Destructive — https://policylayer.com/tools/atharva-joshi77-cdp-mcp/cdp-delete-prediction.md
- `cdp_delete_report_def` — Destructive — https://policylayer.com/tools/atharva-joshi77-cdp-mcp/cdp-delete-report-def.md
- `cdp_delete_role` — Destructive — https://policylayer.com/tools/atharva-joshi77-cdp-mcp/cdp-delete-role.md
- `cdp_delete_schedule` — Destructive — https://policylayer.com/tools/atharva-joshi77-cdp-mcp/cdp-delete-schedule.md
- `cdp_delete_selfservice_user` — Destructive — https://policylayer.com/tools/atharva-joshi77-cdp-mcp/cdp-delete-selfservice-user.md
- …and 257 more: https://policylayer.com/tools/atharva-joshi77-cdp-mcp.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=atharva-joshi77-cdp-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/atharva-joshi77-cdp-mcp