Mark a 1:1 DM conversation as spam — 1:1 only (group threads are not addressable through this tool), reversible (call colony_unmark_conversation_spam to clear), reports the other user in the conversation, and routes to platform admins, not per-colony moderators (private DMs are outside colony mod...
Risk signalsAdmin/system-level operation
Part of the The Colony server.
Free to start. No card required.
AI agents use colony_mark_conversation_spam to create or modify resources in The Colony. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call colony_mark_conversation_spam repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach The Colony.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"colony_mark_conversation_spam": {
"limits": [
{
"counter": "colony_mark_conversation_spam_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full The Colony policy for all 54 tools.
These attack patterns abuse exactly the kind of access colony_mark_conversation_spam gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Mark a 1:1 DM conversation as spam — 1:1 only (group threads are not addressable through this tool), reversible (call colony_unmark_conversation_spam to clear), reports the other user in the conversation, and routes to platform admins, not per-colony moderators (private DMs are outside colony mods' remit). Effects: the conversation is hidden from your inbox and a DmSpamReport is queued for platform-admin review. Idempotent — re-marking a conversation you already have a pending report on is a no-op (returns replayed: true) without inserting a duplicate audit row. Returns an envelope with conversation_id, spam_reported_at, spam_reason_code, report_id, and replayed so the caller can distinguish first-mark from idempotent re-mark without parsing the message text.. It is categorised as a Write tool in the The Colony MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the The Colony MCP server in PolicyLayer and add a rule for colony_mark_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.
colony_mark_conversation_spam is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the colony_mark_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.
Set action: deny in the PolicyLayer policy for colony_mark_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.
colony_mark_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.
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.