Delete a website record
AI agents call delete_website to permanently remove resources in CiviCRM MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes website records from CiviCRM contact data. Data deletion is irreversible and cannot be undone. While the blast radius is somewhat limited (only website records for a single contact), it fits the Destructive category per the classification rules. Severity is high rather than critical because the impact is scoped to a single field type rather than the entire contact or a systemic resource.
From the tool's definition Tool name is 'delete_website' and description states 'Delete a website record'. The verb 'delete' combined with the irreversible nature of removing a contact's website information qualifies this as destructive.
Attacks that exploit this kind of access
Delete a website record. It is categorised as a Destructive tool in the CiviCRM MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the CiviCRM MCP Server MCP server in PolicyLayer and add a rule for delete_website: 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 CiviCRM MCP Server. Nothing to install.
delete_website 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 delete_website 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 delete_website. 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.
delete_website is provided by the CiviCRM MCP Server MCP server (johncallhub/civicrm-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →