get_custom_properties

Get custom document properties from docProps/custom.xml.

SERVERDocx SOURCEsecurityronin/docx-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/securityronin-docx-mcp/get-custom-properties.md

WHAT IT DOES

What get_custom_properties does on Docx

AI agents call get_custom_properties to retrieve information from Docx without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_custom_properties is rated Low

This tool retrieves document metadata properties without side effects. It performs no creation, modification, deletion, or execution of code. The blast radius of misuse is minimal—an AI agent could only read existing document properties, which poses no risk of data destruction, modification, or unintended operations.

From the tool's definition Tool name 'get_custom_properties' with description 'Get custom document properties' indicates retrieval of metadata without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_custom_properties Allowed

get_custom_properties is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_custom_properties": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Docx, apply this rule, and every get_custom_properties call is checked against it from then on.

FAQ

Questions about get_custom_properties

What does the get_custom_properties tool do? +

Get custom document properties from docProps/custom.xml. It is categorised as a Read tool in the Docx MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_custom_properties? +

Register the Docx MCP server in PolicyLayer and add a rule for get_custom_properties: 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 get_custom_properties? +

get_custom_properties is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_custom_properties? +

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

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

get_custom_properties 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

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →