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

remove_share

Delete a share draft by its id (from list_shares).

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

What remove_share does on FeatureBoard

AI agents call remove_share 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_share is rated Critical

This tool permanently deletes a share draft without the ability to recover it. Although the impact is scoped to a specific share draft (not system-wide), deletion is inherently irreversible and falls into the Destructive category.

From the tool's definition 'Delete a share draft by its id' - the tool explicitly performs deletion, which is irreversible. The verb 'remove' combined with 'delete' in the description indicates permanent removal of data.

Questions about remove_share

What does the remove_share tool do? +

Delete a share draft by its id (from list_shares). 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_share? +

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

remove_share 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_share? +

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

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

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