This record as markdown: /tools/io-github-bitsandtea-postking-mcp/delete-theme.md
What delete_theme does on Postking Mcp
AI agents call delete_theme 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_theme is rated Critical
This tool permanently removes a content theme, which cannot be undone. Deletion is irreversible data loss, making it Destructive rather than Write. High severity because accidental deletion by an AI agent could remove important brand content strategies. Confidence is high due to explicit 'Delete' language and clear destructive intent in the description.
From the tool's definition delete_theme: 'Delete a content theme from the active brand.' The verb 'Delete' and description explicitly state irreversible removal of a theme resource.
Attacks that exploit this kind of access
The rule that runs delete_theme 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 delete_theme, this is the rule to start with:
delete_theme is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Postking Mcp, apply this rule, and every delete_theme call is checked against it from then on.
Questions about delete_theme
Delete a content theme from the active brand. 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.
Register the Postking MCP server in PolicyLayer and add a rule for delete_theme: 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.
delete_theme 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_theme 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_theme. 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_theme 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.
Across the catalogue