archive_private_message_thread · Sanka MCP Server MCP

WHAT IT DOES

What archive_private_message_thread does on Sanka MCP Server

AI agents use archive_private_message_thread to create or update resources in Sanka MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sanka MCP Server environment.

WHY IT NEEDS A POLICY

Why archive_private_message_thread needs a policy

While archiving is not a permanent deletion (data still exists), it is a state-changing operation that modifies the user's inbox organization. This does not qualify as Read (no data retrieval only), nor as Destructive (archiving is reversible in most systems—can be unarchived), nor as Execute (not running arbitrary code/commands), nor as Financial. The tool modifies how data is organized/categorized for a user.

From the tool's definition The tool performs an irreversible state change operation: 'Archive an authenticated user private/personal account-level inbox thread in Sanka'.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

archive_private_message_thread Rate-limited

archive_private_message_thread stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "archive_private_message_thread": {
      "limits": [
        {
          "counter": "archive_private_message_thread_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Sanka MCP Server, so you can run agents against it safely.

FAQ

Questions about archive_private_message_thread

What does the archive_private_message_thread tool do? +

Archive an authenticated user private/personal account-level inbox thread in Sanka. Do not use for /conversation or shared workspace inbox threads. It is categorised as a Write tool in the Sanka MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on archive_private_message_thread? +

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

What risk level is archive_private_message_thread? +

archive_private_message_thread is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit archive_private_message_thread? +

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

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

archive_private_message_thread is provided by the Sanka MCP Server MCP server (sankahq/sanka-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.