get_text_document
Read text document details from a named text layer.
This record as markdown: /tools/synthetic-ai-ae-mcp/get-text-document.md
What get_text_document does on Ae
AI agents call get_text_document to retrieve information from Ae without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
compName | string | Yes | Composition name. |
layerName | string | Yes | Text layer name. |
timeoutMs | number | — | Process timeout in milliseconds. Defaults to 120000. |
projectPath | string | — | Optional absolute path to an .aep file to open first. |
Parameters from the server's own tool schema.
Why get_text_document is rated Low
Even though get_text_document only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs get_text_document safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ae, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_text_document, this is the rule to start with:
get_text_document is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Ae, apply this rule, and every get_text_document call is checked against it from then on.
Questions about get_text_document
Read text document details from a named text layer. It is categorised as a Read tool in the Ae MCP Server, which means it retrieves data without modifying state.
get_text_document accepts 4 parameters: compName, layerName, timeoutMs, projectPath. Required: compName, layerName. The full parameter table on this page comes from the server's own tool schema.
Register the Ae MCP server in PolicyLayer and add a rule for get_text_document: 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 Ae. Nothing to install.
get_text_document is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_text_document 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.
Set action: deny in the PolicyLayer policy for get_text_document. 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.
get_text_document is provided by the Ae MCP server (@synthetic-ai/ae-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ae, and thousands of servers like it.
This server
Across the catalogue