Insert a new entry into a Notion database via Relentless API. Data is automatically validated before insertion to catch errors early. Use this to create new documentation, blog posts, leads, or any structured data. The data will be immediately visible in Notion and accessible via the Relentless API.
AI agents use relentless_insert to create or update resources in Relentless MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Relentless MCP Server environment.
This tool creates or modifies data reversibly by inserting new entries into a Notion database. While insertion is a write operation that persists data, it is not destructive (reversible via delete/update), does not execute arbitrary code, and does not involve financial transactions.
From the tool's definition Tool description states 'Insert a new entry into a Notion database' and 'create new documentation, blog posts, leads, or any structured data.' The verb 'insert' combined with 'create' and 'new entry' clearly indicates data creation.
Attacks that exploit this kind of access
Insert a new entry into a Notion database via Relentless API. Data is automatically validated before insertion to catch errors early. Use this to create new documentation, blog posts, leads, or any structured data. The data will be immediately visible in Notion and accessible via the Relentless API. It is categorised as a Write tool in the Relentless MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Relentless MCP Server MCP server in PolicyLayer and add a rule for relentless_insert: 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 Relentless MCP Server. Nothing to install.
relentless_insert 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 relentless_insert 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 relentless_insert. 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.
relentless_insert is provided by the Relentless MCP Server MCP server (pranaythesingh/relentless-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 →