Archive a landing page.
AI agents call keitaro_delete_landing_page to permanently remove resources in Keitaro MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool removes or disables a landing page from active use. Even if technically recoverable from backups, archiving a landing page is an irreversible operational action that cannot be undone through the API itself. The blast radius is high if an agent deletes critical landing pages tied to active campaigns, disrupting traffic flow and revenue.
From the tool's definition Tool name 'keitaro_delete_landing_page' with description 'Archive a landing page' indicates removal of a landing page resource.
Attacks that exploit this kind of access
Archive a landing page. It is categorised as a Destructive tool in the Keitaro MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Keitaro MCP Server MCP server in PolicyLayer and add a rule for keitaro_delete_landing_page: 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 Keitaro MCP Server. Nothing to install.
keitaro_delete_landing_page 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 keitaro_delete_landing_page 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 keitaro_delete_landing_page. 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.
keitaro_delete_landing_page is provided by the Keitaro MCP Server MCP server (keitaromanager/keitaro-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 →