notion_action
Perform a Notion action: search_notion, get_notion_page, get_notion_database, query_notion_database, create_notion_page, update_notion_page.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/notion-action.md
What notion_action does on UnClick
AI agents use notion_action to create or update resources in UnClick, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
query | string | — | |
action | string | Yes | |
filter | object | — | |
parent | object | — | |
api_key | string | — | |
page_id | string | — | |
properties | object | — | |
database_id | string | — |
Parameters from the server's own tool schema.
Why notion_action is rated Medium
The tool spans multiple categories: Read (search, get, query) and Write (create, update). Per the rules, the most severe applicable category is chosen. Since it can create and update Notion pages, it qualifies as Write. There is no evidence of irreversible deletion or financial operations, so Write is the highest applicable category.
From the tool's definition create_notion_page, update_notion_page, search_notion, get_notion_page, get_notion_database, query_notion_database
Risk signalsHandles credentials or secrets (api_key)
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 UnClick, 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 UnClick, apply this rule, and every notion_action call is checked against it from then on.
Questions about notion_action
Perform a Notion action: search_notion, get_notion_page, get_notion_database, query_notion_database, create_notion_page, update_notion_page. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
notion_action accepts 8 parameters: query, action, filter, parent, api_key, page_id, properties, database_id. Required: action. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick 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 UnClick. 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 UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue