View or modify database schema (columns/properties). ## Actions ### "list" (default) — View current schema schema({ database: "Task Board" }) Returns: property names, types, and select/multi_select options. ### "add" — Add a new property schema({ database: "Task Board", action: "add", pr...
Part of the Better Mcp Notion MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents may call schema to permanently remove or destroy resources in Better Mcp Notion. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.
Without a policy, an AI agent could call schema in a loop, permanently destroying resources in Better Mcp Notion. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.
Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.
tools:
schema:
rules:
- action: deny
reason: "Blocked by default — enable with approval"See the full Better Mcp Notion policy for all 9 tools.
Agents calling destructive-class tools like schema have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.
schema is one of the critical-risk operations in Better Mcp Notion. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.
View or modify database schema (columns/properties). ## Actions ### "list" (default) — View current schema schema({ database: "Task Board" }) Returns: property names, types, and select/multi_select options. ### "add" — Add a new property schema({ database: "Task Board", action: "add", property: "Priority", type: "select", options: ["Low", "Medium", "High"] }) ### "remove" — Remove a property schema({ database: "Task Board", action: "remove", property: "Old Column" }) ### "rename" — Rename a property schema({ database: "Task Board", action: "rename", property: "Due", name: "Due Date" }) ## Supported types for add title, rich_text, number, select, multi_select, date, checkbox, url, email, phone_number, status, people, files For select/multi_select, you can provide initial options.. It is categorised as a Destructive tool in the Better Mcp Notion MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Add a rule in your Intercept YAML policy under the tools section for schema. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Better Mcp Notion MCP server.
schema is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the schema rule in your Intercept 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 Intercept policy for schema. 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.
schema is provided by the Better Mcp Notion MCP server (better-mcp-notion). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept