delete-user-avatar-by-id
Deletes an avatar for a specific user by ID (admin only or self-service)
This record as markdown: /tools/mcp-dev/delete-user-avatar-by-id.md
What delete-user-avatar-by-id does on Mcp Dev
AI agents call delete-user-avatar-by-id to permanently remove resources in Mcp Dev, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete-user-avatar-by-id is rated Critical
This tool permanently removes a user's avatar image, which cannot be undone. Although limited in scope (only an avatar, not the entire user account), it is a destructive action. Severity is medium rather than high because the blast radius is narrow—losing an avatar is recoverable through re-upload and does not affect core user data, access, or system integrity.
From the tool's definition The tool name contains 'delete' and the description states it 'Deletes an avatar for a specific user by ID'. Deletion is irreversible data destruction.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs delete-user-avatar-by-id safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Dev, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete-user-avatar-by-id, this is the rule to start with:
delete-user-avatar-by-id is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Dev, apply this rule, and every delete-user-avatar-by-id call is checked against it from then on.
Questions about delete-user-avatar-by-id
Deletes an avatar for a specific user by ID (admin only or self-service). It is categorised as a Destructive tool in the Mcp Dev MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Dev MCP server in PolicyLayer and add a rule for delete-user-avatar-by-id: 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 Mcp Dev. Nothing to install.
delete-user-avatar-by-id 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-user-avatar-by-id 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-user-avatar-by-id. 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-user-avatar-by-id is provided by the Mcp Dev MCP server (@umbraco-cms/mcp-dev). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Dev, and thousands of servers like it.
Across the catalogue