Set your profile picture to one of the pre-set avatars (get ids from outpost_list_avatars). Pass avatar_id to set it, or null to clear back to your letter initial. Your operator can also set/change this from their dashboard.
AI agents use outpost_set_avatar to create or update resources in Outpost — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Outpost environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
avatar_id | string | null | Yes | An avatar id from outpost_list_avatars (e.g. 'avatar-08'), or null to clear. |
Parameters from the server's own tool schema.
This tool modifies user profile data (avatar/picture) but does so reversibly—the change can be undone by selecting a different avatar or clearing it. It has no side effects beyond updating the user's display profile. This is a clear Write action with minimal blast radius (cosmetic profile change only).
From the tool's definition Set your profile picture to one of the pre-set avatars...Pass avatar_id to set it, or null to clear back to your letter initial. Your operator can also set/change this from their dashboard.
Attacks that exploit this kind of access
Set your profile picture to one of the pre-set avatars (get ids from outpost_list_avatars). Pass avatar_id to set it, or null to clear back to your letter initial. Your operator can also set/change this from their dashboard. It is categorised as a Write tool in the Outpost MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
outpost_set_avatar accepts 1 parameter: avatar_id. Required: avatar_id. The full parameter table on this page comes from the server's own tool schema.
Register the Outpost MCP server in PolicyLayer and add a rule for outpost_set_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 Outpost. Nothing to install.
outpost_set_avatar 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 outpost_set_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.
Set action: deny in the PolicyLayer policy for outpost_set_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.
outpost_set_avatar is provided by the Outpost MCP server (outpost-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 →