Delete a post on esa.io
AI agents call posts_delete to permanently remove resources in Mcp Esa Server Python — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs an irreversible delete operation on posts in esa.io, which cannot be undone. Destructive operations have higher severity than Write operations. While the blast radius is contextual (depends on what post is deleted), the irreversible nature and potential loss of documentation content warrants 'high' severity. Confidence is very high given explicit delete semantics in both name and description.
From the tool's definition Tool name 'posts_delete' with description 'Delete a post on esa.io' directly indicates irreversible deletion of data.
Attacks that exploit this kind of access
Delete a post on esa.io. It is categorised as a Destructive tool in the Mcp Esa Server Python MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Esa Server Python MCP server in PolicyLayer and add a rule for posts_delete: 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 Mcp Esa Server Python. Nothing to install.
posts_delete 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 posts_delete 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 posts_delete. 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.
posts_delete is provided by the Mcp Esa Server Python MCP server (scnsh/mcp-esa-server-python). 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 →