update_document_class · IBM Content Services MCP Server MCP

WHAT IT DOES

What update_document_class does on IBM Content Services MCP Server

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

WHY IT NEEDS A POLICY

Why update_document_class needs a policy

The tool modifies document classification metadata within IBM FileNet Content Manager. This is a Write operation because it changes data state reversibly—classification changes can be undone by updating again, unlike deletion. It is not Destructive (no permanent data loss), Execute (no code execution), or Financial.

From the tool's definition Tool name 'update_document_class' indicates modification of document properties. The sibling tools show this server manages document lifecycle operations including create_document, checkin_document, delete_document_version, and delete_hold.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_document_class Rate-limited

update_document_class 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_document_class": {
      "limits": [
        {
          "counter": "update_document_class_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 IBM Content Services MCP Server, so you can run agents against it safely.

FAQ

Questions about update_document_class

What does the update_document_class tool do? +

update_document_class. It is categorised as a Write tool in the IBM Content Services 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_document_class? +

Register the IBM Content Services MCP Server MCP server in PolicyLayer and add a rule for update_document_class: 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 IBM Content Services MCP Server. Nothing to install.

What risk level is update_document_class? +

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

Can I rate-limit update_document_class? +

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

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

update_document_class is provided by the IBM Content Services MCP Server MCP server (mohamedarif-m/filenet-mcp-localfile). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.