Update an existing administrator
AI agents use update_admin to create or update resources in Campaign Monitor MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Campaign Monitor MCP environment.
This tool modifies existing data (administrator account details) in a reversible manner, fitting the Write category. Severity is medium rather than high because while unauthorized admin updates could grant elevated access, the impact depends on what specific admin properties are modified and by whom. The blast radius is constrained to administrative access control rather than data deletion or financial transactions.
From the tool's definition Tool name 'update_admin' and description 'Update an existing administrator' indicate modification of administrative user accounts and their associated permissions or settings.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Update an existing administrator. It is categorised as a Write tool in the Campaign Monitor MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Campaign Monitor MCP server in PolicyLayer and add a rule for update_admin: 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 Campaign Monitor MCP. Nothing to install.
update_admin 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_admin 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_admin. 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_admin is provided by the Campaign Monitor MCP server (pauliowest/cmon-mcp). 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 →