Populate table with data
AI agents use populate_table to create or update resources in Indesign — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Indesign environment.
This tool creates or modifies data within an InDesign document table. The operation is reversible (data can be edited or cleared), so it does not qualify as Destructive. It does not execute arbitrary code or trigger external operations, so it is not Execute. It modifies rather than merely reads, so it is not Read.
From the tool's definition Tool performs 'populate table with data' — modifies document content by inserting/updating data into an existing table structure, which is a reversible write operation consistent with other document modification tools on this server like apply_paragraph_style…
Documented attack patterns abuse exactly the kind of access populate_table gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Indesign, and nothing reaches the server without passing your rules. This is the rule we recommend for populate_table:
{
"version": "1",
"default": "deny",
"tools": {
"populate_table": {
"limits": [
{
"counter": "populate_table_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}populate_table 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.
Free to start. No card required.
Populate table with data. It is categorised as a Write tool in the Indesign MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Indesign MCP server in PolicyLayer and add a rule for populate_table: 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. Nothing to install.
populate_table is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the populate_table 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 populate_table. 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.
populate_table is provided by the Indesign MCP server (lucdesign/indesign-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Indesign, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
36 Indesign tools catalogued and risk-classified — across an index of 43,000+ MCP servers.