# agent_studio_execute_agent_deprecated

Execute Agent (Deprecated)

Agent View of the PolicyLayer registry record for `agent_studio_execute_agent_deprecated`. HTML page: https://policylayer.com/tools/aiwerk-mcp-server-ghl/agent-studio-execute-agent-deprecated

## Facts

- Tool: `agent_studio_execute_agent_deprecated`
- Server: Ghl (`@aiwerk/mcp-server-ghl`) — https://policylayer.com/tools/aiwerk-mcp-server-ghl.md
- Install: `npx -y @aiwerk/mcp-server-ghl`
- Homepage: https://www.npmjs.com/package/@aiwerk/mcp-server-ghl
- Risk category: Execute (High risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 9 (2 required)
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `source` | string | no |  |
| `agentId` | string | yes |  |
| `message` | string | yes | Message to send to the agent |
| `contactId` | string | no | Contact ID to associate with this execution. When provided, contact data will be hydrated and made available to the agent. |
| `versionId` | string | no | Published version ID to execute. If not provided, the latest published production version will be used. |
| `locationId` | string | no | Location ID Defaults to GHL_LOCATION_ID when omitted. |
| `attachments` | array | no | Attachments for the message |
| `executionId` | string | no | Unique session identifier that maintains conversational context across multiple interactions within the same agent session. Omit this field for the first messag |
| `inputVariables` | object | no | Input variables to pass to the agent. These should match the input variables defined in the agent configuration. |

Parameters from the server's own tool schema.

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

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "agent_studio_execute_agent_deprecated",
    "arguments": {
      "agentId": "<agentId>",
      "message": "<message>"
    }
  }
}
```

## Why agent_studio_execute_agent_deprecated is rated High

agent_studio_execute_agent_deprecated triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

## Use case

AI agents invoke agent_studio_execute_agent_deprecated to trigger actions in Ghl. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Ghl:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "agent_studio_execute_agent_deprecated": {
      "limits": [
        {
          "counter": "agent_studio_execute_agent_deprecated_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Ghl (568)

- `ad_manager_fb_delete_ad` — Destructive — https://policylayer.com/tools/aiwerk-mcp-server-ghl/ad-manager-fb-delete-ad.md
- `ad_manager_fb_delete_ad_account` — Destructive — https://policylayer.com/tools/aiwerk-mcp-server-ghl/ad-manager-fb-delete-ad-account.md
- `ad_manager_fb_delete_adset` — Destructive — https://policylayer.com/tools/aiwerk-mcp-server-ghl/ad-manager-fb-delete-adset.md
- `ad_manager_fb_delete_campaign` — Destructive — https://policylayer.com/tools/aiwerk-mcp-server-ghl/ad-manager-fb-delete-campaign.md
- `ad_manager_fb_delete_custom_audience` — Destructive — https://policylayer.com/tools/aiwerk-mcp-server-ghl/ad-manager-fb-delete-custom-audience.md
- `ad_manager_fb_delete_integration` — Destructive — https://policylayer.com/tools/aiwerk-mcp-server-ghl/ad-manager-fb-delete-integration.md
- `ad_manager_fb_delete_page` — Destructive — https://policylayer.com/tools/aiwerk-mcp-server-ghl/ad-manager-fb-delete-page.md
- `ad_manager_fb_remove_custom_audience_member` — Destructive — https://policylayer.com/tools/aiwerk-mcp-server-ghl/ad-manager-fb-remove-custom-audience-member.md
- `ad_manager_google_delete_ad_account` — Destructive — https://policylayer.com/tools/aiwerk-mcp-server-ghl/ad-manager-google-delete-ad-account.md
- `ad_manager_google_delete_conversion` — Destructive — https://policylayer.com/tools/aiwerk-mcp-server-ghl/ad-manager-google-delete-conversion.md
- `ad_manager_google_delete_segment` — Destructive — https://policylayer.com/tools/aiwerk-mcp-server-ghl/ad-manager-google-delete-segment.md
- `ad_manager_li_delete_ad_account` — Destructive — https://policylayer.com/tools/aiwerk-mcp-server-ghl/ad-manager-li-delete-ad-account.md
- `agent_studio_delete_agent` — Destructive — https://policylayer.com/tools/aiwerk-mcp-server-ghl/agent-studio-delete-agent.md
- `associations_delete_association` — Destructive — https://policylayer.com/tools/aiwerk-mcp-server-ghl/associations-delete-association.md
- `associations_delete_relation` — Destructive — https://policylayer.com/tools/aiwerk-mcp-server-ghl/associations-delete-relation.md
- `brand_boards_delete_brand_board` — Destructive — https://policylayer.com/tools/aiwerk-mcp-server-ghl/brand-boards-delete-brand-board.md
- `businesses_delete_business` — Destructive — https://policylayer.com/tools/aiwerk-mcp-server-ghl/businesses-delete-business.md
- `calendars_delete_appointment_note` — Destructive — https://policylayer.com/tools/aiwerk-mcp-server-ghl/calendars-delete-appointment-note.md
- `calendars_delete_calendar` — Destructive — https://policylayer.com/tools/aiwerk-mcp-server-ghl/calendars-delete-calendar.md
- `calendars_delete_calendar_resource` — Destructive — https://policylayer.com/tools/aiwerk-mcp-server-ghl/calendars-delete-calendar-resource.md
- `calendars_delete_event` — Destructive — https://policylayer.com/tools/aiwerk-mcp-server-ghl/calendars-delete-event.md
- `calendars_delete_event_notification` — Destructive — https://policylayer.com/tools/aiwerk-mcp-server-ghl/calendars-delete-event-notification.md
- `calendars_delete_group` — Destructive — https://policylayer.com/tools/aiwerk-mcp-server-ghl/calendars-delete-group.md
- `calendars_delete_schedule` — Destructive — https://policylayer.com/tools/aiwerk-mcp-server-ghl/calendars-delete-schedule.md
- `calendars_remove_calendar_from_schedule` — Destructive — https://policylayer.com/tools/aiwerk-mcp-server-ghl/calendars-remove-calendar-from-schedule.md
- `contacts_delete_contact` — Destructive — https://policylayer.com/tools/aiwerk-mcp-server-ghl/contacts-delete-contact.md
- `contacts_delete_contact_from_workflow` — Destructive — https://policylayer.com/tools/aiwerk-mcp-server-ghl/contacts-delete-contact-from-workflow.md
- `contacts_delete_note` — Destructive — https://policylayer.com/tools/aiwerk-mcp-server-ghl/contacts-delete-note.md
- `contacts_delete_task` — Destructive — https://policylayer.com/tools/aiwerk-mcp-server-ghl/contacts-delete-task.md
- `contacts_remove_contact_from_campaign` — Destructive — https://policylayer.com/tools/aiwerk-mcp-server-ghl/contacts-remove-contact-from-campaign.md
- …and 538 more: https://policylayer.com/tools/aiwerk-mcp-server-ghl.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=aiwerk-mcp-server-ghl · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/aiwerk-mcp-server-ghl