set_expertise

Set the assistant

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-expertise.md

WHAT IT DOES

What set_expertise does on CoWork OS

AI agents use set_expertise 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_expertise is rated Medium

The tool appears to modify assistant settings or expertise configuration, which is reversible data modification. However, confidence is lowered to 0.6 because the description is incomplete ('Set the assistant' is vague) and doesn't explicitly state what is being written or what the scope of modification is.

From the tool's definition Tool name 'set_expertise' and description 'Set the assistant' suggest modification of configuration or state, making this a Write operation that creates or modifies data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs set_expertise 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_expertise, this is the rule to start with:

set_expertise Rate-limited

set_expertise 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_expertise": {
      "limits": [
        {
          "counter": "set_expertise_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_expertise call is checked against it from then on.

FAQ

Questions about set_expertise

What does the set_expertise tool do? +

Set the assistant. 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_expertise? +

Register the CoWork OS MCP server in PolicyLayer and add a rule for set_expertise: 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_expertise? +

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

Can I rate-limit set_expertise? +

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

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

set_expertise 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 →