AI agents use update_contact to create or update resources in AdButler — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AdButler environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | number | Yes | Contact ID |
name | string | — | Contact name |
email | string | — | Contact email address |
notes | string | — | Additional notes |
Parameters from the server's own tool schema.
This tool modifies existing contact records, which is a Write operation. The severity is medium because contact data modifications in an advertising platform could affect campaign targeting, communications, or business relationships, but the change is reversible. High confidence because the intent is clear from both the name and description.
From the tool's definition Tool name 'update_contact' and description 'Update an existing contact' indicate modification of contact data. The verb 'Update' confirms reversible data modification rather than destructive deletion or financial transaction.
Attacks that exploit this kind of access
Update an existing contact. It is categorised as a Write tool in the AdButler MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
update_contact accepts 4 parameters: id, name, email, notes. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the AdButler 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 AdButler. 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 AdButler MCP server (adbutler/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 →