upload-user-current-avatar · Mcp Dev MCP: Risk & Policy

WHAT IT DOES

What upload-user-current-avatar does on Mcp Dev

AI agents use upload-user-current-avatar to create or update resources in Mcp Dev — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Dev environment.

WHY IT NEEDS A POLICY

Why upload-user-current-avatar needs a policy

This tool creates or modifies user profile data (avatar image) in a reversible manner. It modifies the authenticated user's profile but does not delete data or execute arbitrary code. The blast radius is limited to the current user's profile metadata.

From the tool's definition Tool name contains 'upload' and description states 'Uploads an avatar for the current authenticated user', indicating data creation/modification.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

upload-user-current-avatar Rate-limited

upload-user-current-avatar 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": {
    "upload-user-current-avatar": {
      "limits": [
        {
          "counter": "upload-user-current-avatar_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 Mcp Dev, so you can run agents against it safely.

FAQ

Questions about upload-user-current-avatar

What does the upload-user-current-avatar tool do? +

Uploads an avatar for the current authenticated user. It is categorised as a Write tool in the Mcp Dev MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on upload-user-current-avatar? +

Register the Mcp Dev MCP server in PolicyLayer and add a rule for upload-user-current-avatar: 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.

What risk level is upload-user-current-avatar? +

upload-user-current-avatar is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit upload-user-current-avatar? +

Yes. Add a rate_limit block to the upload-user-current-avatar 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 upload-user-current-avatar completely? +

Set action: deny in the PolicyLayer policy for upload-user-current-avatar. 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 upload-user-current-avatar? +

upload-user-current-avatar 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.