Low Risk

get_document_elements

Get all elements in the document

How to control get_document_elements ↓

AI agents call get_document_elements to retrieve information from InDesign UXP MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool retrieves or queries document structure and content without altering any data. It poses minimal risk—the only concern would be if sensitive design information could be leaked, but that is a data sensitivity issue rather than a functional risk category. The tool has no side effects and cannot be misused to damage documents or trigger unintended actions.

From the tool's definition Tool name 'get_document_elements' combined with description 'Get all elements in the document' indicates a query/retrieval operation with no modification or side effects.

Documented attack patterns abuse exactly the kind of access get_document_elements gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and InDesign UXP MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_document_elements:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_document_elements": {}
  }
}

get_document_elements is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register InDesign UXP MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_document_elements tool do? +

Get all elements in the document. It is categorised as a Read tool in the InDesign UXP MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_document_elements? +

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

What risk level is get_document_elements? +

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

Can I rate-limit get_document_elements? +

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

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

get_document_elements is provided by the InDesign UXP MCP Server MCP server (theloniuser/indesign-uxp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every InDesign UXP MCP Server tool call.

Deterministic rules across all 135 InDesign UXP MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

135 InDesign UXP MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.