Replace the entire survey flow tree. Use get_survey_flow first to get the current flow, modify it, then pass the full tree back.
AI agents use update_survey_flow to create or update resources in Qualtrics MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Qualtrics MCP Server environment.
update_survey_flow modifies survey logic and flow structures but does not delete data; changes are reversible by issuing another update. This qualifies as Write rather than Destructive. Severity is high because misconfiguration of survey logic could corrupt survey integrity, affect active surveys, and impact data collection outcomes.
From the tool's definition Tool description states 'Replace the entire survey flow tree' and 'pass the full tree back' — this modifies the survey's logic and structure irreversibly in terms of survey state, but the action itself is reversible (can be undone by updating again).
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access update_survey_flow gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Qualtrics MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for update_survey_flow:
{
"version": "1",
"default": "deny",
"tools": {
"update_survey_flow": {
"limits": [
{
"counter": "update_survey_flow_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_survey_flow 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.
Free to start. No card required.
Replace the entire survey flow tree. Use get_survey_flow first to get the current flow, modify it, then pass the full tree back. It is categorised as a Write tool in the Qualtrics MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Qualtrics MCP Server MCP server in PolicyLayer and add a rule for update_survey_flow: 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 Qualtrics MCP Server. Nothing to install.
update_survey_flow 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_flow 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_flow. 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_flow is provided by the Qualtrics MCP Server MCP server (yrvelez/qualtrics-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Qualtrics MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
57 Qualtrics MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.