libi.get_piece_state

Returns whether the piece has uncommitted draft changes, when the current snapshot was committed, and the last 10 prior snapshots in the safety-net history.

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.get-piece-state.md

WHAT IT DOES

What libi.get_piece_state does on Libi

AI agents use libi.get_piece_state 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.get_piece_state is rated Medium

An AI agent can call libi.get_piece_state faster than any human can review: one bad instruction and it creates or modifies resources in Libi by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

libi.get_piece_state Rate-limited

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

FAQ

Questions about libi.get_piece_state

What does the libi.get_piece_state tool do? +

Returns whether the piece has uncommitted draft changes, when the current snapshot was committed, and the last 10 prior snapshots in the safety-net history. 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.get_piece_state? +

Register the Libi MCP server in PolicyLayer and add a rule for libi.get_piece_state: 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.get_piece_state? +

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

Can I rate-limit libi.get_piece_state? +

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

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

libi.get_piece_state 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 →