# brand_truth_delete A destructive tool on the Postking Mcp MCP server. Agent View of the PolicyLayer registry record for `brand_truth_delete`. HTML page: https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/brand-truth-delete ## Facts - Tool: `brand_truth_delete` - Server: Postking Mcp (`postking-mcp`) — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp.md - Install: `npx -y postking-mcp` - Homepage: https://github.com/bitsandtea/postking-mcp - Risk category: Destructive (Critical risk) - Registry record: grade D, identity unverified - Server auth posture: gated - Server CORS policy: * - Server rate-limited: no - Parameters: 0 - Recommended policy verdict: Hidden ## Example call (MCP tools/call, JSON-RPC 2.0) ```json { "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "brand_truth_delete", "arguments": {} } } ``` ## Why brand_truth_delete is rated Critical Delete operations are irreversible by nature and fall into the Destructive category. The empty description lowers confidence slightly, but the explicit 'delete' in the tool name and the context of a brand management system make it clear this performs destructive actions. If misused by an AI agent, it could permanently remove critical brand configuration or data. From the tool's own definition: "Tool name is 'brand_truth_delete' which explicitly indicates a delete operation. Given the server's purpose of managing brands and content, this tool likely irreversibly removes brand identity or configuration data." ## Use case AI agents call brand_truth_delete 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. ## Recommended policy (PolicyLayer) Verdict: **Hidden**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Postking Mcp: ```json { "version": "1", "default": "deny", "hide": [ "brand_truth_delete" ] } ``` ## Other tools on Postking Mcp (224) - `cancel_job` — Destructive — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/cancel-job.md - `competitor_delete` — Destructive — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/competitor-delete.md - `delete_asset` — Destructive — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/delete-asset.md - `delete_blog_article` — Destructive — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/delete-blog-article.md - `delete_domain` — Destructive — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/delete-domain.md - `delete_landing_page` — Destructive — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/delete-landing-page.md - `delete_lp_version` — Destructive — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/delete-lp-version.md - `delete_post` — Destructive — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/delete-post.md - `delete_side_page` — Destructive — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/delete-side-page.md - `delete_theme` — Destructive — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/delete-theme.md - `delete_weekly_schedule` — Destructive — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/delete-weekly-schedule.md - `knowledge_delete` — Destructive — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/knowledge-delete.md - `logout` — Destructive — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/logout.md - `revoke_api_key` — Destructive — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/revoke-api-key.md - `seo_delete_keyword` — Destructive — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/seo-delete-keyword.md - `seo_roadmap_delete` — Destructive — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/seo-roadmap-delete.md - `storyline_delete` — Destructive — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/storyline-delete.md - `storyline_delete_line_item` — Destructive — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/storyline-delete-line-item.md - `template_delete` — Destructive — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/template-delete.md - `competitor_refresh` — Execute — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/competitor-refresh.md - `generate_connect_link` — Execute — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/generate-connect-link.md - `generate_text` — Execute — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/generate-text.md - `generate_themes` — Execute — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/generate-themes.md - `run_weekly_schedule_day` — Execute — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/run-weekly-schedule-day.md - `seo_generate_clusters` — Execute — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/seo-generate-clusters.md - `storyline_execute` — Execute — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/storyline-execute.md - `storyline_regenerate_line_item` — Execute — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/storyline-regenerate-line-item.md - `billing_subscribe` — Financial — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/billing-subscribe.md - `billing_topup` — Financial — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/billing-topup.md - `billing_list_packs` — Read — https://policylayer.com/tools/io-github-bitsandtea-postking-mcp/billing-list-packs.md - …and 194 more: https://policylayer.com/tools/io-github-bitsandtea-postking-mcp.md ## For agents This record is a snapshot. Live verdicts and the full registry: - Check every server in your MCP config at once: `npx -y policylayer stack` - Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md) - Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events` --- Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=io-github-bitsandtea-postking-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/io-github-bitsandtea-postking-mcp