create_outlet
Create a shop outlet/location. Optionally pass id to preserve a legacy UUID during migration.
This record as markdown: /tools/io-favcrm-favcrm/create-outlet.md
What create_outlet does on FavCRM
AI agents use create_outlet 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 |
|---|---|---|---|
id | string | — | Optional outlet UUID (for legacy migration; non-standard formats accepted) |
name | string | Yes | Outlet name |
phone | object | — | Contact phone |
address | object | — | Street address |
logoUrl | object | — | Logo URL |
isActive | boolean | — | Whether outlet is active (default true) |
latitude | object | — | Latitude |
longitude | object | — | Longitude |
sortOrder | integer | — | Display sort order (default 0) |
acceptsOrders | boolean | — | Whether outlet accepts online orders (default true) |
Parameters from the server's own tool schema.
Why create_outlet is rated Medium
The tool creates new records in the CRM database, which classifies it as a Write operation. It is reversible (outlets can be archived or deleted later) and does not irreversibly destroy data or execute arbitrary code.
From the tool's definition Tool description explicitly states 'Create a shop outlet/location' with optional id parameter. This creates new organizational data (a physical outlet/location record) in the CRM system.
Risk signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
The rule that runs create_outlet 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_outlet, this is the rule to start with:
create_outlet 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_outlet call is checked against it from then on.
Questions about create_outlet
Create a shop outlet/location. Optionally pass id to preserve a legacy UUID during migration. 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_outlet accepts 10 parameters: id, name, phone, address, logoUrl, isActive, latitude, longitude, sortOrder, acceptsOrders. Required: name. 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_outlet: 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_outlet 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_outlet 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_outlet. 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_outlet 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