Update an existing contact in a mailing list
AI agents use update_contact 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.
This tool modifies contact information in a mailing list, which is a reversible write operation. It does not delete data (would be Destructive), does not move money (would be Financial), and does not execute arbitrary code (would be Execute).
From the tool's definition Tool name is 'update_contact' and description states 'Update an existing contact in a mailing list'. The verb 'update' indicates modification of existing data.
Documented attack patterns abuse exactly the kind of access update_contact 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_contact:
{
"version": "1",
"default": "deny",
"tools": {
"update_contact": {
"limits": [
{
"counter": "update_contact_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} update_contact 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 contact in a mailing list. 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_contact: 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_contact 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_contact 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_contact. 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_contact 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.