unlink_customer_ticket
Remove a ticket link from a CRM company.
This record as markdown: /tools/ai-featureboard-featureboard/unlink-customer-ticket.md
What unlink_customer_ticket does on FeatureBoard
AI agents use unlink_customer_ticket to create or update resources in FeatureBoard, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FeatureBoard environment.
Why unlink_customer_ticket is rated Medium
This tool removes an association/link between a ticket and a CRM company. While it deletes a relationship record, it is typically a reversible operation (the link can be re-created), so it falls under Write rather than Destructive. Misuse could disrupt CRM data integrity but has limited blast radius.
From the tool's definition Remove a ticket link from a CRM company
Attacks that exploit this kind of access
The rule that runs unlink_customer_ticket 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 unlink_customer_ticket, this is the rule to start with:
unlink_customer_ticket stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect FeatureBoard, apply this rule, and every unlink_customer_ticket call is checked against it from then on.
Questions about unlink_customer_ticket
Remove a ticket link from a CRM company. It is categorised as a Write tool in the FeatureBoard MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the FeatureBoard MCP server in PolicyLayer and add a rule for unlink_customer_ticket: 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.
unlink_customer_ticket is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the unlink_customer_ticket 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 unlink_customer_ticket. 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.
unlink_customer_ticket 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.
This server
Across the catalogue