list_survey_workflows
List automation workflows attached to a survey.
This record as markdown: /tools/io-favcrm-favcrm/list-survey-workflows.md
What list_survey_workflows does on FavCRM
AI agents call list_survey_workflows to retrieve information from FavCRM without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
surveyId | string | Yes | Survey ID |
Parameters from the server's own tool schema.
Why list_survey_workflows is rated Low
This tool retrieves or queries existing automation workflow data associated with a survey. It produces no side effects, creates no new data, executes no code, and makes no destructive or financial changes. It is a straightforward data retrieval operation, appropriate for the Read category.
From the tool's definition Tool name is 'list_survey_workflows' and description states it 'List automation workflows attached to a survey' — the verb 'list' and action of retrieving/querying workflows are characteristic of read-only operations with no data modification.
Attacks that exploit this kind of access
The rule that runs list_survey_workflows 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 list_survey_workflows, this is the rule to start with:
list_survey_workflows is read-only, so it stays allowed. 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 list_survey_workflows call is checked against it from then on.
Questions about list_survey_workflows
List automation workflows attached to a survey. It is categorised as a Read tool in the FavCRM MCP Server, which means it retrieves data without modifying state.
list_survey_workflows accepts 1 parameter: surveyId. 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 list_survey_workflows: 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.
list_survey_workflows is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_survey_workflows 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 list_survey_workflows. 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.
list_survey_workflows 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