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

WHAT IT DOES

What template_delete does on Postking Mcp

AI agents call template_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 template_delete is rated Critical

The name 'template_delete' clearly signals a destructive action. While the description is empty and provides no additional confirmation, the naming convention and the platform's focus on content management (brands, posts, scheduling, blogs) indicate this tool permanently removes templates, which cannot be undone. This fits the Destructive category as it irreversibly deletes data.

From the tool's definition Tool name is 'template_delete' which explicitly indicates deletion. In the context of a content management and publishing platform (PostKing MCP), template deletion is an irreversible operation that removes stored content resources.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs template_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 template_delete, this is the rule to start with:

template_delete Hidden

template_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": [
    "template_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 template_delete call is checked against it from then on.

FAQ

Questions about template_delete

What does the template_delete tool do? +

template_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 template_delete? +

Register the Postking MCP server in PolicyLayer and add a rule for template_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 template_delete? +

template_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 template_delete? +

Yes. Add a rate_limit block to the template_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 template_delete completely? +

Set action: deny in the PolicyLayer policy for template_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 template_delete? +

template_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 template_delete does on Postking Mcp

Why template_delete is rated Critical

The rule that runs template_delete safely

Questions about template_delete

More on Postking, and thousands of servers like it.