update_collection_item · Skema MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_collection_item does on Skema MCP Server

AI agents use update_collection_item to create or update resources in Skema MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Skema MCP Server environment.

WHY IT NEEDS A POLICY

Why update_collection_item needs a policy

This tool creates or modifies data reversibly by updating an existing collection item with partial merge semantics. It does not delete data (which would be Destructive) nor execute arbitrary code (which would be Execute). The modification is reversible through subsequent updates. Severity is medium because misuse could corrupt or alter important CMS content, but the effect is limited to a single item and reversible.

From the tool's definition Tool name 'update_collection_item' and description 'Met à jour un item existant (merge partiel)' [Updates an existing item (partial merge)] indicate modification of existing data in a CMS collection.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_collection_item Rate-limited

update_collection_item 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_collection_item": {
      "limits": [
        {
          "counter": "update_collection_item_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Skema MCP Server, so you can run agents against it safely.

FAQ

Questions about update_collection_item

What does the update_collection_item tool do? +

Met à jour un item existant (merge partiel). It is categorised as a Write tool in the Skema MCP Server 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_collection_item? +

Register the Skema MCP Server MCP server in PolicyLayer and add a rule for update_collection_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 Skema MCP Server. Nothing to install.

What risk level is update_collection_item? +

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

Can I rate-limit update_collection_item? +

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

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

update_collection_item is provided by the Skema MCP Server MCP server (skemacms/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.