# cdp_create_role Create a new role with whitelist/blacklist permissions. Pass whitelist/blacklist as JSON arrays of Permission objects. Agent View of the PolicyLayer registry record for `cdp_create_role`. HTML page: https://policylayer.com/tools/atharva-joshi77-cdp-mcp/cdp-create-role ## Facts - Tool: `cdp_create_role` - 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: Write (Medium risk) - Registry record: grade F, identity unverified - Server rate-limited: no - Parameters: 0 - Recommended policy verdict: Rate-limited ## Example call (MCP tools/call, JSON-RPC 2.0) ```json { "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "cdp_create_role", "arguments": {} } } ``` ## Why cdp_create_role is rated Medium This tool creates new security roles with permission configurations in an administrative CDP system. While reversible (roles can be deleted or modified), creating roles—especially with broad permissions—has high blast radius in a multi-tenant environment. Misuse could grant unauthorized access to sensitive customer data or administrative functions. From the tool's own definition: "Tool name 'cdp_create_role' and description explicitly states 'Create a new role', which creates new data. The tool accepts whitelist/blacklist permission configurations, indicating it establishes access control policies that affect system security posture." ## Use case AI agents use cdp_create_role to create or update resources in CDP MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CDP MCP Server environment. ## Recommended policy (PolicyLayer) Verdict: **Rate-limited**. 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_create_role": { "limits": [ { "counter": "cdp_create_role_rate", "window": "minute", "max": 30, "scope": "grant" } ] } } } ``` ## 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