Medium Risk

update_library_item

Update an existing content library item.

Risk signalsHigh parameter count (10 properties)

Part of the SendIt server.

update_library_item can modify SendIt data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE SENDIT →

Free to start. No card required.

AI agents use update_library_item to create or modify resources in SendIt. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call update_library_item repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach SendIt.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_library_item": {
      "limits": [
        {
          "counter": "update_library_item_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full SendIt policy for all 148 tools.

Get this rule live on your own SendIt server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY SENDIT →

View all 148 tools →

These attack patterns abuse exactly the kind of access update_library_item gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so update_library_item only ever does what you allow.

SECURE SENDIT →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the update_library_item tool do? +

Update an existing content library item.. It is categorised as a Write tool in the SendIt 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_library_item? +

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

What risk level is update_library_item? +

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

Can I rate-limit update_library_item? +

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

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

update_library_item is provided by the SendIt MCP server (https://sendit.infiniteappsai.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every SendIt tool call.

Deterministic rules across all 148 SendIt tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.