archive_note · Slite MCP Server MCP: Risk & Policy

WHAT IT DOES

What archive_note does on Slite MCP Server

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

WHY IT NEEDS A POLICY

Why archive_note needs a policy

Archiving is a Write operation because it modifies the note's state and visibility but does not destroy data or prevent recovery. It's reversible (can unarchive), distinguishing it from Destructive actions like delete_note which is also present on this server. Severity is medium because archiving can impact team knowledge management and visibility, but the data remains intact and recoverable.

From the tool's definition Tool performs 'Archive or unarchive a note' — a state change operation that modifies note metadata/status without irreversibly deleting data. The note remains accessible and the action is reversible.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

archive_note Rate-limited

archive_note 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_note": {
      "limits": [
        {
          "counter": "archive_note_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 Slite MCP Server, so you can run agents against it safely.

FAQ

Questions about archive_note

What does the archive_note tool do? +

Archive or unarchive a note in Slite. It is categorised as a Write tool in the Slite 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_note? +

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

What risk level is archive_note? +

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

Can I rate-limit archive_note? +

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

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

archive_note is provided by the Slite MCP Server MCP server (takeokunn/slite-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.