Delete a self-serve OAuth developer client. DESTRUCTIVE: prevents new authorizations for that client_id; existing access tokens remain revocable as API keys.
AI agents call delete_oauth_client 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 removes an OAuth client configuration, which prevents future authorizations and cannot be undone. While existing access tokens remain revocable, the deletion of the client itself is irreversible and disruptive.
From the tool's definition Tool description explicitly states 'Delete a self-serve OAuth developer client' and marks it 'DESTRUCTIVE: prevents new authorizations for that client_id'.
Attacks that exploit this kind of access
Delete a self-serve OAuth developer client. DESTRUCTIVE: prevents new authorizations for that client_id; existing access tokens remain revocable as API 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_oauth_client: 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_oauth_client 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_oauth_client 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_oauth_client. 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_oauth_client 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 →