set_user_name

Store the user

SERVERCoWork OS SOURCECoWork-OS/CoWork-OS

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cowork-os/set-user-name.md

WHAT IT DOES

What set_user_name does on CoWork OS

AI agents use set_user_name to create or update resources in CoWork OS, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CoWork OS environment.

RISK

Why set_user_name is rated Medium

This tool creates or modifies user profile data (the username/user identity), which is reversible and has limited blast radius. It does not execute code, delete data, move money, or trigger external operations. The action is a straightforward data write operation. Confidence is slightly reduced due to the terse description, but the intent is clear from the name.

From the tool's definition Tool name 'set_user_name' and description 'Store the user' indicate data creation/modification of user profile information.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs set_user_name safely

PolicyLayer is an MCP gateway: it sits between your AI agents and CoWork OS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set_user_name, this is the rule to start with:

set_user_name Rate-limited

set_user_name 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": {
    "set_user_name": {
      "limits": [
        {
          "counter": "set_user_name_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect CoWork OS, apply this rule, and every set_user_name call is checked against it from then on.

FAQ

Questions about set_user_name

What does the set_user_name tool do? +

Store the user. It is categorised as a Write tool in the CoWork OS MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_user_name? +

Register the CoWork OS MCP server in PolicyLayer and add a rule for set_user_name: 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 CoWork OS. Nothing to install.

What risk level is set_user_name? +

set_user_name is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit set_user_name? +

Yes. Add a rate_limit block to the set_user_name 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 set_user_name completely? +

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

set_user_name is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on CoWork OS, and thousands of servers like it.

This server

All 342 CoWork OS tools →

Across the catalogue

set-prioity on Kanban MCP Server →team_manager_set_sources on Team Manager MCP →qt_set_property on Qt → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →