ticket_customers

Reverse lookup: which CRM companies a board ticket is linked to (surfaces the ticket↔customer relationship).

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

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What ticket_customers does on FeatureBoard

AI agents call ticket_customers to retrieve information from FeatureBoard without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why ticket_customers is rated Low

This tool purely retrieves relationship data between tickets and CRM companies. It performs a read/query operation with no side effects, modifications, or deletions. The description explicitly frames it as a 'lookup' that 'surfaces' existing relationships.

From the tool's definition Reverse lookup: which CRM companies a board ticket is linked to (surfaces the ticket↔customer relationship)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

ticket_customers Allowed

ticket_customers is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ticket_customers": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about ticket_customers

What does the ticket_customers tool do? +

Reverse lookup: which CRM companies a board ticket is linked to (surfaces the ticket↔customer relationship). It is categorised as a Read tool in the FeatureBoard MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on ticket_customers? +

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

ticket_customers is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit ticket_customers? +

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

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

ticket_customers 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

aiva_search_customers on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →