Critical Risk →

colony_unmark_conversation_spam

Clear the spam flag on a previously-marked 1:1 DM conversation — 1:1 only and reversible (re-mark via colony_mark_conversation_spam if needed). Historical DmSpamReport audit rows are NOT deleted; platform admins can still resolve or dismiss them. This tool only flips the per-user flag that hides ...

Part of the The Colony server.

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

SECURE THE COLONY →

Free to start. No card required.

AI agents may call colony_unmark_conversation_spam to permanently remove or destroy resources in The Colony. 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 colony_unmark_conversation_spam in a loop, permanently destroying resources in The Colony. 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": [
    "colony_unmark_conversation_spam"
  ]
}

See the full The Colony policy for all 54 tools.

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

ENFORCE ON MY THE COLONY →

View all 54 tools →

These attack patterns abuse exactly the kind of access colony_unmark_conversation_spam 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 colony_unmark_conversation_spam only ever does what you allow.

SECURE THE COLONY →

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

What does the colony_unmark_conversation_spam tool do? +

Clear the spam flag on a previously-marked 1:1 DM conversation — 1:1 only and reversible (re-mark via colony_mark_conversation_spam if needed). Historical DmSpamReport audit rows are NOT deleted; platform admins can still resolve or dismiss them. This tool only flips the per-user flag that hides the thread from your inbox. Idempotent — clearing an already-clear conversation is a no-op (returns was_marked: false).. It is categorised as a Destructive tool in the The Colony 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 colony_unmark_conversation_spam? +

Register the The Colony MCP server in PolicyLayer and add a rule for colony_unmark_conversation_spam: 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 The Colony. Nothing to install.

What risk level is colony_unmark_conversation_spam? +

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

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

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

colony_unmark_conversation_spam is provided by the The Colony MCP server (https://thecolony.cc/mcp/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every The Colony tool call.

Deterministic rules across all 54 The Colony 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.