Revoke a Posterly API key owned by the authenticated user. DESTRUCTIVE: call whoami or use a known key ID, show the user the exact key ID/prefix/name if available, and get explicit confirmation before calling. Cannot revoke the key currently authenticating this request, OAuth-issued keys, or mana...
AI agents call delete_api_key to permanently remove resources in Posterly — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes authentication credentials, which cannot be undone. The description's explicit 'DESTRUCTIVE' label and warning about confirmation requirements confirms this is an irreversible operation. While restricted by authentication context (cannot revoke the active key), revocation of other API keys causes permanent loss of access credentials, fitting the Destructive category.
From the tool's definition Tool description explicitly states 'DESTRUCTIVE' and 'Revoke a Posterly API key'. Revoking an API key irreversibly destroys authentication credentials, preventing future access.
Attacks that exploit this kind of access
Revoke a Posterly API key owned by the authenticated user. DESTRUCTIVE: call whoami or use a known key ID, show the user the exact key ID/prefix/name if available, and get explicit confirmation before calling. Cannot revoke the key currently authenticating this request, OAuth-issued keys, or managed assistant keys. It is categorised as a Destructive tool in the Posterly MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Posterly MCP server in PolicyLayer and add a rule for delete_api_key: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Posterly. Nothing to install.
delete_api_key is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_api_key rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for delete_api_key. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
delete_api_key is provided by the Posterly MCP server (posterly-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →