Critical Risk →

crm_delete_social_category

Delete a social media post category.

Part of the 0nmcp server.

crm_delete_social_category can permanently delete data in 0nmcp, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE 0NMCP →

Free to start. No card required.

AI agents may call crm_delete_social_category to permanently remove or destroy resources in 0nmcp. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call crm_delete_social_category in a loop, permanently destroying resources in 0nmcp. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "crm_delete_social_category"
  ]
}

See the full 0nmcp policy for all 407 tools.

Get this rule live on your own 0nmcp server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY 0NMCP →

View all 407 tools →

These attack patterns abuse exactly the kind of access crm_delete_social_category gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so crm_delete_social_category only ever does what you allow.

SECURE 0NMCP →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the crm_delete_social_category tool do? +

Delete a social media post category.. It is categorised as a Destructive tool in the 0nmcp 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 crm_delete_social_category? +

Register the 0n MCP server in PolicyLayer and add a rule for crm_delete_social_category: 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 0nmcp. Nothing to install.

What risk level is crm_delete_social_category? +

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

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

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

crm_delete_social_category is provided by the 0n MCP server (0nmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every 0nmcp tool call.

Deterministic rules across all 407 0nmcp tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.