update_website · CiviCRM MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_website does on CiviCRM MCP Server

AI agents use update_website to create or update resources in CiviCRM MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CiviCRM MCP Server environment.

WHY IT NEEDS A POLICY

Why update_website needs a policy

This tool modifies existing website records associated with contacts or entities in CiviCRM, which is a Write operation. It is reversible and does not delete data or execute arbitrary code, so it does not qualify as Destructive or Execute. The blast radius is medium because incorrect website updates could affect contact information accuracy and communication, but the change can be undone by updating again.

From the tool's definition Tool name 'update_website' and description 'Update an existing website record' indicate modification of existing data. The action is reversible (websites can be updated again or reverted), and is part of a broader contact/entity management system (CiviCRM).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_website Rate-limited

update_website 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_website": {
      "limits": [
        {
          "counter": "update_website_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches CiviCRM MCP Server, so you can run agents against it safely.

FAQ

Questions about update_website

What does the update_website tool do? +

Update an existing website record. It is categorised as a Write tool in the CiviCRM MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_website? +

Register the CiviCRM MCP Server MCP server in PolicyLayer and add a rule for update_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.

What risk level is update_website? +

update_website is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_website? +

Yes. Add a rate_limit block to the update_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.

How do I block update_website completely? +

Set action: deny in the PolicyLayer policy for update_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.

What MCP server provides update_website? +

update_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.