Create a recurring task in a Notion database
AI agents use notion_create_recurring_task to create or update resources in Notion MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Notion MCP Server environment.
This tool creates a new recurring task object within Notion, modifying the database by adding structured data. While this is a Write operation (creates/adds data reversibly), the severity is medium rather than low because recurring tasks can affect workflow automation and scheduling.
From the tool's definition Tool name contains 'create' and description states 'Create a recurring task in a Notion database', which creates new data in a reversible manner.
Attacks that exploit this kind of access
Create a recurring task in a Notion database. It is categorised as a Write tool in the Notion MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Notion MCP Server MCP server in PolicyLayer and add a rule for notion_create_recurring_task: 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 MCP Server. Nothing to install.
notion_create_recurring_task 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_create_recurring_task 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_create_recurring_task. 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_create_recurring_task is provided by the Notion MCP Server MCP server (tkc/notion-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →