New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

remove_product

Remove a product from a board

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-product.md

What remove_product does on FeatureBoard

AI agents call remove_product 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.

Why remove_product is rated Critical

The verb 'remove' combined with the action of deleting a product from a project board indicates an irreversible data deletion operation. This exceeds Write category (which is reversible) and qualifies as Destructive. While the blast radius is limited to a single product entity, the irreversibility and potential loss of associated project data warrants high severity.

From the tool's definition Tool name contains 'remove' which indicates irreversible deletion. Description states 'Remove a product from a board' - removing a product is a destructive operation that cannot be undone and eliminates data permanently.

Questions about remove_product

What does the remove_product tool do? +

Remove a product from a board. 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_product? +

Register the FeatureBoard MCP server in PolicyLayer and add a rule for remove_product: 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_product? +

remove_product 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_product? +

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

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

remove_product 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.

More on FeatureBoard, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of FeatureBoard's. Pull the full record:

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.