archive_private_message_thread
Archive an authenticated user private/personal account-level inbox thread in Sanka. Do not use for /conversation or shared workspace inbox threads.
This record as markdown: /tools/sankahq-sanka-mcp/archive-private-message-thread.md
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 archive_private_message_thread is rated Medium
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
The rule that runs archive_private_message_thread safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sanka MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For archive_private_message_thread, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Sanka MCP Server, apply this rule, and every archive_private_message_thread call is checked against it from then on.
Questions about archive_private_message_thread
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.
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.
archive_private_message_thread 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 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.
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.
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.
More on Sanka MCP Server, and thousands of servers like it.
This server
Across the catalogue