libi.update_piece_name

Set the name (and optionally description) of the current piece. Respects the nameSetByUser flag — if the user has manually named the piece, the name will not be overwritten.

SERVERLibi SOURCENagellabs/libi

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/libi/libi.update-piece-name.md

WHAT IT DOES

What libi.update_piece_name does on Libi

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

RISK

Why libi.update_piece_name is rated Medium

Modifies metadata reversibly; no destruction, financial impact, or code execution involved.

From the tool's definition Set the name and optionally description of the current piece.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs libi.update_piece_name safely

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

libi.update_piece_name Rate-limited

libi.update_piece_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": {
    "libi.update_piece_name": {
      "limits": [
        {
          "counter": "libi.update_piece_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 Libi, apply this rule, and every libi.update_piece_name call is checked against it from then on.

FAQ

Questions about libi.update_piece_name

What does the libi.update_piece_name tool do? +

Set the name (and optionally description) of the current piece. Respects the nameSetByUser flag — if the user has manually named the piece, the name will not be overwritten. It is categorised as a Write tool in the Libi MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on libi.update_piece_name? +

Register the Libi MCP server in PolicyLayer and add a rule for libi.update_piece_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 Libi. Nothing to install.

What risk level is libi.update_piece_name? +

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

Can I rate-limit libi.update_piece_name? +

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

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

libi.update_piece_name is provided by the Libi MCP server (Nagellabs/libi). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Libi, and thousands of servers like it.

This server

All 215 Libi tools →

Across the catalogue

The MCP Attack Database →

Guides

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