Get the full survey flow tree showing the order of blocks, embedded data, web services, branching, and randomization
AI agents call get_survey_flow to retrieve information from Qualtrics MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays the structure and configuration of a survey's flow without making any changes to the survey, executing code, or triggering external operations. It is a straightforward read operation that returns configuration metadata about how a survey is structured. There are no side effects, no data modification, and no execution of logic—only data retrieval.
From the tool's definition Tool name 'get_survey_flow' and description 'Get the full survey flow tree' indicate a retrieval operation with no modification, deletion, or execution of external actions.
Documented attack patterns abuse exactly the kind of access get_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 get_survey_flow:
{
"version": "1",
"default": "deny",
"tools": {
"get_survey_flow": {}
}
}get_survey_flow is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the full survey flow tree showing the order of blocks, embedded data, web services, branching, and randomization. It is categorised as a Read tool in the Qualtrics MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Qualtrics MCP Server MCP server in PolicyLayer and add a rule for get_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.
get_survey_flow 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 get_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 get_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.
get_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.