update_survey
Update a survey draft or publishing configuration. Use questionBlocks to replace the ordered form block list.
This record as markdown: /tools/io-favcrm-favcrm/update-survey.md
What update_survey does on FavCRM
AI agents use update_survey 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 |
|---|---|---|---|
slug | string | — | URL slug |
title | string | — | Survey title |
openAt | object | — | Optional ISO datetime when the survey opens |
status | string | — | Survey status |
closeAt | object | — | Optional ISO datetime when the survey closes |
settings | object | — | Survey settings such as allowMultipleResponses, collectEmail, collectIpAddress, requireAuthentication, showProgress, successMessage |
surveyId | string | Yes | Survey ID |
visibility | string | — | Survey access mode |
description | object | — | Survey description |
questionBlocks | array | — | Ordered survey question blocks |
Parameters from the server's own tool schema.
Why update_survey is rated Medium
The tool updates survey data reversibly (drafts and configurations can be modified or reverted). It does not delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or merely read data (Read).
From the tool's definition Tool description states 'Update a survey draft or publishing configuration' and 'replace the ordered form block list' — these are modification operations on existing data structures.
Risk signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
The rule that runs update_survey 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_survey, this is the rule to start with:
update_survey 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_survey call is checked against it from then on.
Questions about update_survey
Update a survey draft or publishing configuration. Use questionBlocks to replace the ordered form block list. 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_survey accepts 10 parameters: slug, title, openAt, status, closeAt, settings, surveyId, visibility, description, questionBlocks. Required: 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 update_survey: 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_survey 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_survey 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_survey. 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_survey 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