lock_content_control

Lock a content control to prevent editing.

SERVERDocx SOURCEsecurityronin/docx-mcp

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/securityronin-docx-mcp/lock-content-control.md

WHAT IT DOES

What lock_content_control does on Docx

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

RISK

Why lock_content_control is rated Medium

This tool modifies document state by changing the locked/unlocked status of a content control. While it prevents editing rather than deleting, it is a Write operation (state modification) rather than Read. Severity is medium because an AI agent misusing this could restrict legitimate document editing, but the action is reversible (content controls can be unlocked).

From the tool's definition Tool name 'lock_content_control' indicates modification of document properties; description states it will 'prevent editing' of a content control, which is a reversible state change to document structure/permissions.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs lock_content_control safely

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

lock_content_control Rate-limited

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

FAQ

Questions about lock_content_control

What does the lock_content_control tool do? +

Lock a content control to prevent editing. It is categorised as a Write tool in the Docx MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on lock_content_control? +

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

What risk level is lock_content_control? +

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

Can I rate-limit lock_content_control? +

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

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

lock_content_control is provided by the Docx MCP server (securityronin/docx-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Docx, and thousands of servers like it.

This server

All 219 Docx tools →

Across the catalogue

The MCP Attack Database →

Guides

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