Add a Web Service element to the survey flow that makes an HTTP call to an external API during survey execution. Response values can be mapped to embedded data fields for use in subsequent questions via piped text. The web service is inserted at the position you specify (default: before the first...
AI agents invoke add_web_service to trigger actions in Qualtrics MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers an outbound HTTP request to an arbitrary external API when the survey runs. This is Execute-category because it performs a network call to an external service whose effects depend on the target URL and payload — the consequences are determined by what that external API does, which could include writing data, triggering workflows, or other side effects beyond Qualtrics itself.
From the tool's definition makes an HTTP call to an external API during survey execution
Documented attack patterns abuse exactly the kind of access add_web_service 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 add_web_service:
{
"version": "1",
"default": "deny",
"tools": {
"add_web_service": {
"limits": [
{
"counter": "add_web_service_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}add_web_service stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Add a Web Service element to the survey flow that makes an HTTP call to an external API during survey execution. Response values can be mapped to embedded data fields for use in subsequent questions via piped text. The web service is inserted at the position you specify (default: before the first block). It is categorised as a Execute tool in the Qualtrics MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Qualtrics MCP Server MCP server in PolicyLayer and add a rule for add_web_service: 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.
add_web_service is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the add_web_service 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 add_web_service. 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.
add_web_service 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.