AI agents use archive_page to create or update resources in Notion API MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Notion API MCP Server environment.
Archiving is a state change (Write category) rather than permanent deletion (Destructive). While it removes a page from active view, it is reversible—archived pages can be restored. This affects data organization and visibility, warranting medium severity. High confidence based on clear intent to modify page status.
From the tool's definition Tool name 'archive_page' and description 'Archive a Notion page' indicates a modification operation that moves a page to archive status, which is reversible (pages can be unarchived).
Documented attack patterns abuse exactly the kind of access archive_page gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Notion API MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for archive_page:
{
"version": "1",
"default": "deny",
"tools": {
"archive_page": {
"limits": [
{
"counter": "archive_page_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}archive_page 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.
Free to start. No card required.
Archive a Notion page. It is categorised as a Write tool in the Notion API MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Notion API MCP Server MCP server in PolicyLayer and add a rule for archive_page: 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 Notion API MCP Server. Nothing to install.
archive_page 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_page 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_page. 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_page is provided by the Notion API MCP Server MCP server (pbohannon/notion-api-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Notion API MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
17 Notion API MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.