delete_side_page

Delete a side page. Pass confirm: true to proceed.

SERVERPostking Mcp SOURCEpostking-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/io-github-bitsandtea-postking-mcp/delete-side-page.md

What delete_side_page does on Postking Mcp

AI agents call delete_side_page to permanently remove resources in Postking Mcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_side_page is rated Critical

This tool removes data permanently from the system. Even though it's scoped to 'side pages' rather than the entire system, deletion operations that cannot be reversed are classified as Destructive. The confirmation requirement shows awareness of the irreversible nature. An AI agent misusing this could remove important content pages without recovery options, making this high severity.

From the tool's definition delete_side_page deletes a side page irreversibly. The description explicitly states 'Delete' and requires confirmation (confirm: true), indicating an action that cannot be undone.

Questions about delete_side_page

What does the delete_side_page tool do? +

Delete a side page. Pass confirm: true to proceed. It is categorised as a Destructive tool in the Postking Mcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_side_page? +

Register the Postking MCP server in PolicyLayer and add a rule for delete_side_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 Postking Mcp. Nothing to install.

What risk level is delete_side_page? +

delete_side_page is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_side_page? +

Yes. Add a rate_limit block to the delete_side_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.

How do I block delete_side_page completely? +

Set action: deny in the PolicyLayer policy for delete_side_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.

What MCP server provides delete_side_page? +

delete_side_page is provided by the Postking MCP server (postking-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Postking, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Postking's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.