mailerpress-pro/update-embed-key updates the metadata of an existing embed API key: its name, allowed domain, status and rate limits.
It cannot re-issue the raw key value.
At a glance
| Ability | mailerpress-pro/update-embed-key |
| Toolset | MailerPress Pro — toolset/mailerpress-pro |
| Group | MailerPress Pro › Embed Keys |
| Requires | AcrossAI Pro, plus MailerPress with its Pro add-on active on the site |
| Capability | manage_options |
| Safety | Writes data |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Pro 0.9.16 and later |
How it works
The useful operations here are tightening and disabling. Adding a domain restriction to a key that has none, or lowering a rate limit, takes effect immediately and without redeploying anything — the key in the embed stays the same.
Disabling by status is the reversible alternative to deletion. A key suspected of being abused can be switched off, the effect observed, and switched back on if it was innocent.
What this cannot do is rotate. There is no way to change the key value while keeping the record, so a compromised key means creating a new one, updating the embed, and deleting the old.
Changing the allowed domain on a key that is in use breaks the embed immediately if the new domain is wrong — and the failure appears on the other site, as a form that stops submitting.
Idempotent.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
id | integer | Yes | The key record. |
name | string | No | A new name. |
allowed_domain | string | No | A new domain restriction. |
status | string | No | Enable or disable the key. |
rate_limit | integer | No | A new rate limit. |
What comes back
| Name | Type | What it is |
|---|---|---|
key | object | The key metadata after the write. No raw value. |
success | boolean | Whether the call completed. |
message | string | A one-line summary of what happened, suitable for showing a human. |
error_code | string | Present only on failure — a stable machine-readable reason, such as a missing field, a wrong field type or an unmet confirmation. |
Example
Ask your assistant:
Restrict that embed key to our domain.
It resolves to one call:
{
"ability": "mailerpress-pro/update-embed-key",
"parameters": {
"id": 3,
"allowed_domain": "example.com"
}
}Worth knowing
- Tightening a restriction takes effect without redeploying the embed.
- Disabling is the reversible alternative to deletion.
- There is no rotation — a compromised key means create, replace, delete.
- A wrong domain breaks the form on the other site, silently from here.
Related abilities
- MailerPress Pro List Embed Keys — read the current scope
- MailerPress Pro Delete Embed Key — revoke it
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category