find_or_create_workroom_thread
Find or create a Workroom DM thread between a merchant user and an AI colleague. Use this when an inbound event deserves owner attention but no threadId was provided. This only prepares an internal Workroom channel.
This record as markdown: /tools/io-favcrm-favcrm/find-or-create-workroom-thread.md
What find_or_create_workroom_thread does on FavCRM
AI agents use find_or_create_workroom_thread 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 |
|---|---|---|---|
title | string | — | Optional title if a new thread is created |
userId | string | — | Merchant user ID to notify. Defaults to the current MCP user when omitted. |
agentId | string | Yes | AI colleague ID for the Workroom DM |
Parameters from the server's own tool schema.
Why find_or_create_workroom_thread is rated Medium
The tool either retrieves an existing thread (Read) or creates a new one (Write). Since creation is a possible outcome and Write is more severe than Read, the tool is classified as Write. The blast radius is medium: misuse could flood internal channels with unwanted threads, but it does not delete data or trigger financial actions.
From the tool's definition 'Find or create a Workroom DM thread' — creates a new internal messaging thread if one does not exist
Attacks that exploit this kind of access
The rule that runs find_or_create_workroom_thread 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 find_or_create_workroom_thread, this is the rule to start with:
find_or_create_workroom_thread 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 find_or_create_workroom_thread call is checked against it from then on.
Questions about find_or_create_workroom_thread
Find or create a Workroom DM thread between a merchant user and an AI colleague. Use this when an inbound event deserves owner attention but no threadId was provided. This only prepares an internal Workroom channel. 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.
find_or_create_workroom_thread accepts 3 parameters: title, userId, agentId. Required: agentId. 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 find_or_create_workroom_thread: 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.
find_or_create_workroom_thread 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 find_or_create_workroom_thread 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 find_or_create_workroom_thread. 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.
find_or_create_workroom_thread 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