Delete a specific page from an agent.
AI agents call delete_page to permanently remove resources in CustomGPT MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool performs an irreversible deletion operation on a page resource within an agent. Deletion cannot be undone and represents data loss. This falls squarely into the Destructive category, which is more severe than Write (reversible modifications). The high severity reflects that an agent's pages could contain important configuration, content, or knowledge data whose loss would impact agent functionality.
From the tool's definition Tool name 'delete_page' combined with description 'Delete a specific page from an agent' explicitly indicates irreversible deletion of data.
Attacks that exploit this kind of access
Delete a specific page from an agent. It is categorised as a Destructive tool in the CustomGPT MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the CustomGPT MCP Server MCP server in PolicyLayer and add a rule for delete_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 CustomGPT MCP Server. Nothing to install.
delete_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 delete_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 delete_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.
delete_page is provided by the CustomGPT MCP Server MCP server (poll-the-people/customgpt-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 →