create_ticket
Create a support ticket for a member issue.
This record as markdown: /tools/io-favcrm-favcrm/create-ticket.md
What create_ticket does on FavCRM
AI agents use create_ticket to create or update resources in FavCRM, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FavCRM environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
source | string | — | Where the ticket originated |
subject | string | Yes | Ticket subject/title |
category | string | — | Ticket category |
priority | string | — | Ticket priority |
accountId | string | — | Member/account ID this ticket is about |
contactName | string | — | Contact name if no account ID |
description | string | — | Detailed description of the issue |
contactEmail | string | — | Contact email if no account ID |
contactPhone | string | — | Contact phone if no account ID |
Parameters from the server's own tool schema.
Why create_ticket is rated Medium
This tool creates a new support ticket record, which is a reversible write operation. It does not execute code, delete data irreversibly, move funds, or query existing data. The severity is medium because misuse could generate numerous spam tickets or create false support records, but the impact is recoverable—tickets can be edited, deleted, or marked as spam.
From the tool's definition Tool name 'create_ticket' combined with description 'Create a support ticket for a member issue' indicates data creation. The verb 'Create' is a write operation that generates a new record (support ticket) in the system.
Attacks that exploit this kind of access
The rule that runs create_ticket safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FavCRM, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_ticket, this is the rule to start with:
create_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 FavCRM, apply this rule, and every create_ticket call is checked against it from then on.
Questions about create_ticket
Create a support ticket for a member issue. It is categorised as a Write tool in the FavCRM MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_ticket accepts 9 parameters: source, subject, category, priority, accountId, contactName, description, contactEmail, contactPhone. Required: subject. The full parameter table on this page comes from the server's own tool schema.
Register the FavCRM MCP server in PolicyLayer and add a rule for create_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 FavCRM. Nothing to install.
create_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 create_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 create_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.
create_ticket is provided by the FavCRM MCP server (https://api.favcrm.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FavCRM, and thousands of servers like it.
This server
Across the catalogue