remove_page

Delete a sub-page (by slug) and its rendered file. The home page can

SERVERFeatureBoard SOURCEhttps://github.com/valentil/featureboard-mcp/releases/download/v0.7/featureboard.plugin

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ai-featureboard-featureboard/remove-page.md

WHAT IT DOES

What remove_page does on FeatureBoard

AI agents call remove_page to permanently remove resources in FeatureBoard, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why remove_page is rated Critical

The tool explicitly deletes data ('Delete a sub-page') and removes rendered files, which are irreversible operations. This is a destructive action that cannot be undone, fitting the Destructive category. The severity is high because deletion of project board pages could lose work or documentation, though the impact is scoped to individual pages rather than entire systems.

From the tool's definition Delete a sub-page (by slug) and its rendered file

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs remove_page safely

PolicyLayer is an MCP gateway: it sits between your AI agents and FeatureBoard, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For remove_page, this is the rule to start with:

remove_page Hidden

remove_page is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "remove_page"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect FeatureBoard, apply this rule, and every remove_page call is checked against it from then on.

FAQ

Questions about remove_page

What does the remove_page tool do? +

Delete a sub-page (by slug) and its rendered file. The home page can. It is categorised as a Destructive tool in the FeatureBoard 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 remove_page? +

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

What risk level is remove_page? +

remove_page 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 remove_page? +

Yes. Add a rate_limit block to the remove_page 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 remove_page completely? +

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

remove_page is provided by the FeatureBoard MCP server (https://github.com/valentil/featureboard-mcp/releases/download/v0.7/featureboard.plugin). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on FeatureBoard, and thousands of servers like it.

This server

All 215 FeatureBoard tools → Critical-risk tools on this server →

Across the catalogue

remove_video on Mcptube Vision →remove_2fa on cPanel MCP Server →remove_concept on MegaMemory →task_assignees_remove on Vikunja → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →