update_outlet
Update an existing shop outlet/location by ID.
This record as markdown: /tools/io-favcrm-favcrm/update-outlet.md
What update_outlet does on FavCRM
AI agents use update_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 | Yes | Outlet ID (UUID) |
name | string | — | Outlet name |
phone | object | — | Contact phone |
address | object | — | Street address |
logoUrl | object | — | Logo URL |
isActive | boolean | — | Whether outlet is active |
latitude | object | — | Latitude |
longitude | object | — | Longitude |
sortOrder | integer | — | Display sort order |
acceptsOrders | boolean | — | Whether outlet accepts online orders |
Parameters from the server's own tool schema.
Why update_outlet is rated Medium
This tool creates or modifies data without irreversibly deleting it, placing it in the Write category. Severity is high because updating outlet/location data in a CRM can affect customer routing, business operations, staff assignments, and service delivery.
From the tool's definition Tool performs 'Update an existing shop outlet/location' which modifies data. The action is reversible (can be updated again) and affects business-critical location information in a CRM system serving service businesses.
Risk signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
The rule that runs update_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 update_outlet, this is the rule to start with:
update_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 update_outlet call is checked against it from then on.
Questions about update_outlet
Update an existing shop outlet/location by ID. 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.
update_outlet accepts 10 parameters: id, name, phone, address, logoUrl, isActive, latitude, longitude, sortOrder, acceptsOrders. Required: id. 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 update_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.
update_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 update_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 update_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.
update_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