Register an agent target
create_targetRegister an agent you own or are authorized to test as a target for security assessments. Supply exactly one of: 'config' (the connection config of an endpoint that answers without a key: one live probe fires and the target is saved only if it succeeds); 'url' (a page of yours that your agent's chat lives on: a headless browser discovers the agent behind it, returning status=discovering and a discovery_token to poll with get_target_discovery, or status=not_a_page when the url is already an API endpoint, then supply it as a 'config'); or 'discovery_token' (plus 'candidate' when get_target_discovery listed more than one) to save a discovered candidate, whose session stays on the server. A rejected URL or a failed probe stores nothing and returns a categorized error (invalid_url / unreachable / auth_failed / parse_error / no_reply / not_an_endpoint). This tool asks for no keys, tokens or passwords: an agent that needs one is added in the Enoki app at https://app.enokilabs.ai/inventory (Add integration), which is also the fix for an auth_failed probe on an agent that needs one. Call get_setup_guide first for the workflow and the config field reference. Check list_targets first (a matching name + endpoint_host in the same environment is the same target, so reuse its model_id; if only one of them matches, confirm with your user before creating). A target's connection has no update or delete over MCP; change it in the Enoki app. Its profile is read and changed with get_target_profile and update_target_profile. The response never echoes your config. Requires the write scope; the full setup flow also needs read, for get_setup_guide and list_targets.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | A page of yours that your agent's chat lives on, to discover the agent behind it. | |
| name | No | Display name for the target; required with 'config' or 'discovery_token'. | |
| config | No | The endpoint's connection config (endpoint_url, response_field, transport, ...); its fields are in get_setup_guide and the create_target_schema resource. | |
| candidate | No | Index of the discovered candidate to save, when there is more than one. | |
| environment | No | Where the agent runs. | staging |
| discovery_token | No | Id of the discovery job a create_target call with 'url' started. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| status | Yes | 'created' when a target was saved, 'discovering' for a page, 'not_a_page' when the url is an endpoint to supply as a config. | |
| message | No | Human-facing note. | |
| model_id | No | The target's id, when status=created. | |
| connected | No | Whether the probe read a reply. | |
| discovery_token | No | Poll it with get_target_discovery, when status=discovering. |