update_lore

Record a notable shared moment or reference in the workspace lore. Use after significant accomplishments,

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/update-lore.md

WHAT IT DOES

What update_lore does on CoWork OS

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

This tool creates or modifies lore entries within the workspace, which is a reversible operation. There is no indication of destructive deletion, code execution, financial transactions, or side effects beyond storing metadata about workspace moments.

From the tool's definition Tool name is 'update_lore' and description states 'Record a notable shared moment or reference in the workspace lore.' The verb 'Record' combined with 'update' indicates creation or modification of data (lore entries).

Attacks that exploit this kind of access

RECOMMENDED RULE

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

update_lore Rate-limited

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

FAQ

Questions about update_lore

What does the update_lore tool do? +

Record a notable shared moment or reference in the workspace lore. Use after significant accomplishments,. 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 update_lore? +

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

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

Can I rate-limit update_lore? +

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

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

update_lore 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

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

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