notion_source_remove_property

Remove a property from a configured source schema by setting it to null. Requires confirm=true. Notion does not allow removing the title property.

Server Notion DB MCP Helper trisetiohidayat/notion-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What notion_source_remove_property does on Notion DB MCP Helper

AI agents call notion_source_remove_property to permanently remove resources in Notion DB MCP Helper — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why notion_source_remove_property needs a policy

Removing a schema property is an irreversible structural change — it destroys the property definition (and likely its data) across all rows in the database. The explicit 'confirm=true' requirement signals the operation is destructive and cannot be undone. This maps to Destructive, with high severity given the blast radius of eliminating a column from a Notion database.

From the tool's definition 'Remove a property from a configured source schema by setting it to null. Requires confirm=true.'

Questions about notion_source_remove_property

What does the notion_source_remove_property tool do? +

Remove a property from a configured source schema by setting it to null. Requires confirm=true. Notion does not allow removing the title property. It is categorised as a Destructive tool in the Notion DB MCP Helper MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on notion_source_remove_property? +

Register the Notion DB MCP Helper MCP server in PolicyLayer and add a rule for notion_source_remove_property: 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 DB MCP Helper. Nothing to install.

What risk level is notion_source_remove_property? +

notion_source_remove_property is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit notion_source_remove_property? +

Yes. Add a rate_limit block to the notion_source_remove_property 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.

How do I block notion_source_remove_property completely? +

Set action: deny in the PolicyLayer policy for notion_source_remove_property. 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.

What MCP server provides notion_source_remove_property? +

notion_source_remove_property is provided by the Notion DB MCP Helper MCP server (trisetiohidayat/notion-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.