archive_survey
Archive a survey and remove it from active survey lists.
This record as markdown: /tools/io-favcrm-favcrm/archive-survey.md
What archive_survey does on FavCRM
AI agents use archive_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 |
|---|---|---|---|
surveyId | string | Yes | Survey ID to archive |
Parameters from the server's own tool schema.
Why archive_survey is rated Medium
Archiving is a write operation that modifies survey status but does not permanently destroy data or cause irreversible changes. The survey remains in the system, just hidden from active lists. This is less severe than destructive operations (which would permanently delete), though it does modify data.
From the tool's definition Tool name 'archive_survey' and description states it will 'Archive a survey and remove it from active survey lists.' Archiving is a reversible modification operation that changes the state/visibility of data without permanently deleting it.
Attacks that exploit this kind of access
The rule that runs archive_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 archive_survey, this is the rule to start with:
archive_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 archive_survey call is checked against it from then on.
Questions about archive_survey
Archive a survey and remove it from active survey lists. 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.
archive_survey 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 archive_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.
archive_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 archive_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 archive_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.
archive_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