AI agents use update_question 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.
The tool creates or modifies data (survey questions) in a reversible manner. While it affects survey structure and could impact survey results if modified after distribution, it does not delete data (which would be Destructive) or execute arbitrary code (which would be Execute).
From the tool's definition Tool name 'update_question' with description 'Update an existing question' indicates modification of existing survey question data. This is a reversible write operation on Qualtrics survey content.
Documented attack patterns abuse exactly the kind of access update_question 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_question:
{
"version": "1",
"default": "deny",
"tools": {
"update_question": {
"limits": [
{
"counter": "update_question_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_question 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.
Update an existing question. 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_question: 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_question 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_question 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_question. 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_question 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.