AI agents call remove_contact to permanently remove resources in Qualtrics MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs an irreversible deletion operation on contact data. While the blast radius is somewhat limited to a single contact record rather than bulk data, removal of contacts from mailing lists is a destructive action that cannot be automatically reversed.
From the tool's definition Tool name 'remove_contact' combined with description 'Remove a contact from a mailing list' indicates irreversible deletion of contact data. The action cannot be easily undone and permanently removes a record.
Documented attack patterns abuse exactly the kind of access remove_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 remove_contact:
{
"version": "1",
"default": "deny",
"hide": [
"remove_contact"
]
} remove_contact disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Remove a contact from a mailing list. It is categorised as a Destructive tool in the Qualtrics MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Qualtrics MCP Server MCP server in PolicyLayer and add a rule for remove_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.
remove_contact is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_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 remove_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.
remove_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.