remove_contact
Remove a contact from a company by its contact id (e.g. c1).
This record as markdown: /tools/ai-featureboard-featureboard/remove-contact.md
What remove_contact does on FeatureBoard
AI agents call remove_contact 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_contact is rated Critical
Deletion of contact records is an irreversible operation that destroys data. While the blast radius is constrained to a single contact entity (not system-wide), loss of contact information can disrupt business relationships and CRM workflows. This is more severe than Write (which is reversible) but less critical than Financial operations, warranting high severity.
From the tool's definition Tool name is 'remove_contact' and description states 'Remove a contact from a company' — the verb 'remove' indicates deletion of data that cannot be restored without external intervention.
Attacks that exploit this kind of access
The rule that runs remove_contact 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_contact, this is the rule to start with:
remove_contact is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect FeatureBoard, apply this rule, and every remove_contact call is checked against it from then on.
Questions about remove_contact
Remove a contact from a company by its contact id (e.g. c1). 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.
Register the FeatureBoard MCP server in PolicyLayer and add a rule for remove_contact: 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.
remove_contact 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 remove_contact 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.
Set action: deny in the PolicyLayer policy for remove_contact. 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.
remove_contact 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.
Across the catalogue