Delete a specific post
AI agents call mixpost_delete_post to permanently remove resources in Mixpost — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a post is an irreversible action that permanently removes content from the social media management system. This cannot be undone and represents data loss. While not as critical as system-wide deletion (mixpost_delete_multiple_posts is also present), deleting individual posts is still a destructive operation warranting high severity due to potential impact on social media presence and archived content loss.
From the tool's definition Tool name is 'mixpost_delete_post' with description 'Delete a specific post'. The verb 'delete' is explicit and indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a specific post. It is categorised as a Destructive tool in the Mixpost MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mixpost MCP server in PolicyLayer and add a rule for mixpost_delete_post: 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 Mixpost. Nothing to install.
mixpost_delete_post 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 mixpost_delete_post 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 mixpost_delete_post. 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.
mixpost_delete_post is provided by the Mixpost MCP server (pfarag/mixpost-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 →