competitor_delete

A destructive tool on the Postking MCP server.

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/competitor-delete.md

WHAT IT DOES

What competitor_delete does on Postking Mcp

AI agents call competitor_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.

RISK

Why competitor_delete is rated Critical

The 'delete' suffix combined with the context of brand management strongly suggests this tool performs irreversible deletion. Without a description to confirm the exact scope, but given the clear destructive naming pattern (consistent with 'brand_truth_delete' among sibling tools), this is classified as Destructive rather than Write.

From the tool's definition Tool named 'competitor_delete' with no description provided. The verb 'delete' indicates irreversible removal of data. In the context of a PostKing MCP server managing brands and content, this likely deletes competitor records or related data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs competitor_delete safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Postking Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For competitor_delete, this is the rule to start with:

competitor_delete Hidden

competitor_delete is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "competitor_delete"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Postking Mcp, apply this rule, and every competitor_delete call is checked against it from then on.

FAQ

Questions about competitor_delete

What does the competitor_delete tool do? +

competitor_delete is a destructive tool on the Postking MCP server. 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 competitor_delete? +

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

What risk level is competitor_delete? +

competitor_delete 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 competitor_delete? +

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

How do I block competitor_delete completely? +

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

What MCP server provides competitor_delete? +

competitor_delete 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.

KEEP EXPLORING

What competitor_delete does on Postking Mcp

Why competitor_delete is rated Critical

The rule that runs competitor_delete safely

Questions about competitor_delete

More on Postking, and thousands of servers like it.