link_customer_ticket

Link a board ticket (feature/bug) to a CRM company, stored on the company so it shows in its customer_portal. De-duplicated.

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

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ai-featureboard-featureboard/link-customer-ticket.md

WHAT IT DOES

What link_customer_ticket does on FeatureBoard

AI agents use link_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.

RISK

Why link_customer_ticket is rated Medium

The tool creates a relationship/association between a ticket and a CRM company. This is a reversible write operation (linking), not destructive, financial, or executing code. De-duplication implies idempotent behavior, further confirming it's a benign write. Blast radius is low as it only affects how a ticket is displayed in a customer portal.

From the tool's definition Link a board ticket (feature/bug) to a CRM company, stored on the company so it shows in its customer_portal. De-duplicated.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs link_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 link_customer_ticket, this is the rule to start with:

link_customer_ticket Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "link_customer_ticket": {
      "limits": [
        {
          "counter": "link_customer_ticket_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about link_customer_ticket

What does the link_customer_ticket tool do? +

Link a board ticket (feature/bug) to a CRM company, stored on the company so it shows in its customer_portal. De-duplicated. 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.

How do I enforce a policy on link_customer_ticket? +

Register the FeatureBoard MCP server in PolicyLayer and add a rule for link_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.

What risk level is link_customer_ticket? +

link_customer_ticket is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit link_customer_ticket? +

Yes. Add a rate_limit block to the link_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.

How do I block link_customer_ticket completely? +

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

What MCP server provides link_customer_ticket? +

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

KEEP EXPLORING

More on FeatureBoard, and thousands of servers like it.

This server

All 215 FeatureBoard tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →