upsert_survey_workflow
Create or update a survey automation workflow, usually triggered by survey_response_submitted.
This record as markdown: /tools/io-favcrm-favcrm/upsert-survey-workflow.md
What upsert_survey_workflow does on FavCRM
AI agents use upsert_survey_workflow 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 |
|---|---|---|---|
name | string | Yes | Workflow name |
graph | object | Yes | Workflow graph definition |
status | string | — | Workflow status |
trigger | string | — | Trigger name, default from graph.trigger |
surveyId | string | Yes | Survey ID |
workflowId | string | — | Existing workflow ID when updating |
Parameters from the server's own tool schema.
Why upsert_survey_workflow is rated Medium
This tool modifies data reversibly by creating new survey workflows or updating existing ones. It is a Write operation rather than Execute because it configures automation rules rather than directly triggering external actions.
From the tool's definition Tool name contains 'upsert' (create or update operation) and description states 'Create or update a survey automation workflow'
Attacks that exploit this kind of access
The rule that runs upsert_survey_workflow 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 upsert_survey_workflow, this is the rule to start with:
upsert_survey_workflow 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 upsert_survey_workflow call is checked against it from then on.
Questions about upsert_survey_workflow
Create or update a survey automation workflow, usually triggered by survey_response_submitted. 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.
upsert_survey_workflow accepts 6 parameters: name, graph, status, trigger, surveyId, workflowId. Required: name, graph, surveyId. 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 upsert_survey_workflow: 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.
upsert_survey_workflow 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 upsert_survey_workflow 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 upsert_survey_workflow. 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.
upsert_survey_workflow 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