# marketo_delete_lead

Permanently delete a lead by its numeric ID. This action cannot be undone.

Agent View of the PolicyLayer registry record for `marketo_delete_lead`. HTML page: https://policylayer.com/tools/alexleventer-marketo-mcp/marketo-delete-lead

## Facts

- Tool: `marketo_delete_lead`
- Server: Marketo MCP Server (`alexleventer/marketo-mcp`) — https://policylayer.com/tools/alexleventer-marketo-mcp.md
- Homepage: https://github.com/alexleventer/marketo-mcp
- Risk category: Destructive (Critical risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Hidden

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

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

## Why marketo_delete_lead is rated Critical

The tool irreversibly deletes lead data from Marketo. The description explicitly states the deletion is permanent and cannot be undone, which is the defining characteristic of the Destructive category. While not financial in itself, the loss of customer/prospect data could have significant business impact.

From the tool's own definition: "'Permanently delete a lead by its numeric ID. This action cannot be undone.'"

## Use case

AI agents call marketo_delete_lead to permanently remove resources in Marketo MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "marketo_delete_lead"
  ]
}
```

## Other tools on Marketo MCP Server (26)

- `marketo_delete_channel` — Destructive — https://policylayer.com/tools/alexleventer-marketo-mcp/marketo-delete-channel.md
- `marketo_send_sample_email` — Execute — https://policylayer.com/tools/alexleventer-marketo-mcp/marketo-send-sample-email.md
- `marketo_get_channel_by_id` — Read — https://policylayer.com/tools/alexleventer-marketo-mcp/marketo-get-channel-by-id.md
- `marketo_get_channels` — Read — https://policylayer.com/tools/alexleventer-marketo-mcp/marketo-get-channels.md
- `marketo_get_email_by_id` — Read — https://policylayer.com/tools/alexleventer-marketo-mcp/marketo-get-email-by-id.md
- `marketo_get_emails` — Read — https://policylayer.com/tools/alexleventer-marketo-mcp/marketo-get-emails.md
- `marketo_get_form_by_id` — Read — https://policylayer.com/tools/alexleventer-marketo-mcp/marketo-get-form-by-id.md
- `marketo_get_forms` — Read — https://policylayer.com/tools/alexleventer-marketo-mcp/marketo-get-forms.md
- `marketo_get_lead_activities` — Read — https://policylayer.com/tools/alexleventer-marketo-mcp/marketo-get-lead-activities.md
- `marketo_get_lead_by_email` — Read — https://policylayer.com/tools/alexleventer-marketo-mcp/marketo-get-lead-by-email.md
- `marketo_get_lead_by_id` — Read — https://policylayer.com/tools/alexleventer-marketo-mcp/marketo-get-lead-by-id.md
- `marketo_get_lead_changes` — Read — https://policylayer.com/tools/alexleventer-marketo-mcp/marketo-get-lead-changes.md
- `marketo_get_lead_lists` — Read — https://policylayer.com/tools/alexleventer-marketo-mcp/marketo-get-lead-lists.md
- `marketo_get_program_by_id` — Read — https://policylayer.com/tools/alexleventer-marketo-mcp/marketo-get-program-by-id.md
- `marketo_get_program_members` — Read — https://policylayer.com/tools/alexleventer-marketo-mcp/marketo-get-program-members.md
- `marketo_get_programs` — Read — https://policylayer.com/tools/alexleventer-marketo-mcp/marketo-get-programs.md
- `marketo_get_smart_list_by_id` — Read — https://policylayer.com/tools/alexleventer-marketo-mcp/marketo-get-smart-list-by-id.md
- `marketo_get_smart_lists` — Read — https://policylayer.com/tools/alexleventer-marketo-mcp/marketo-get-smart-lists.md
- `marketo_add_lead_to_list` — Write — https://policylayer.com/tools/alexleventer-marketo-mcp/marketo-add-lead-to-list.md
- `marketo_approve_form` — Write — https://policylayer.com/tools/alexleventer-marketo-mcp/marketo-approve-form.md
- `marketo_clone_form` — Write — https://policylayer.com/tools/alexleventer-marketo-mcp/marketo-clone-form.md
- `marketo_clone_program` — Write — https://policylayer.com/tools/alexleventer-marketo-mcp/marketo-clone-program.md
- `marketo_create_channel` — Write — https://policylayer.com/tools/alexleventer-marketo-mcp/marketo-create-channel.md
- `marketo_create_or_update_lead` — Write — https://policylayer.com/tools/alexleventer-marketo-mcp/marketo-create-or-update-lead.md
- `marketo_remove_lead_from_list` — Write — https://policylayer.com/tools/alexleventer-marketo-mcp/marketo-remove-lead-from-list.md
- `marketo_update_channel` — Write — https://policylayer.com/tools/alexleventer-marketo-mcp/marketo-update-channel.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=alexleventer-marketo-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/alexleventer-marketo-mcp
