notion_action
Use the connected Notion account to search, read, and update pages/data sources.
This record as markdown: /tools/cowork-os/notion-action.md
What notion_action does on CoWork OS
AI agents use notion_action to create or update resources in CoWork OS, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CoWork OS environment.
Why notion_action is rated Medium
The tool performs read operations (search, read) which would normally be 'Read' category, but the explicit mention of 'update' capability elevates this to 'Write' since it can create or modify data reversibly.
From the tool's definition Tool description states it can 'search, read, and update pages/data sources' in Notion. The 'update' capability indicates modification of data.
Attacks that exploit this kind of access
The rule that runs notion_action safely
PolicyLayer is an MCP gateway: it sits between your AI agents and CoWork OS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For notion_action, this is the rule to start with:
notion_action 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 CoWork OS, apply this rule, and every notion_action call is checked against it from then on.
Questions about notion_action
Use the connected Notion account to search, read, and update pages/data sources. It is categorised as a Write tool in the CoWork OS MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the CoWork OS MCP server in PolicyLayer and add a rule for notion_action: 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 CoWork OS. Nothing to install.
notion_action 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 notion_action 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 notion_action. 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.
notion_action is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on CoWork OS, and thousands of servers like it.
This server
Across the catalogue