Delete a campaign on PostEverywhere. Posts in the campaign survive — their campaign_id is set to NULL.
AI agents call delete_campaign to permanently remove resources in Posteverywhere — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion is inherently destructive and irreversible. Although the blast radius is constrained (posts remain accessible, only the campaign container is removed), the action still constitutes permanent data loss of campaign configuration, scheduling metadata, and organizational structure. This warrants Destructive category and high severity due to potential operational disruption and loss of campaign analytics/history.
From the tool's definition Tool name 'delete_campaign' and description states it 'Delete[s] a campaign' — an irreversible removal operation.
Attacks that exploit this kind of access
Delete a campaign on PostEverywhere. Posts in the campaign survive — their campaign_id is set to NULL. It is categorised as a Destructive tool in the Posteverywhere MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Posteverywhere MCP server in PolicyLayer and add a rule for delete_campaign: 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 Posteverywhere. Nothing to install.
delete_campaign 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_campaign 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_campaign. 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_campaign is provided by the Posteverywhere MCP server (posteverywhere/mcp). 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 →