Plan a DOCX table write-back before applying structural changes.
AI agents use docx_table_edit_plan to create or update resources in Asset Aware — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Asset Aware environment.
The tool plans modifications to DOCX table structures (write-back), which creates or modifies data reversibly. While it's described as planning (not immediate execution), it is a write operation targeting document tables. Severity is medium because inadvertent table edits could corrupt document structure or data, but changes are typically reversible via undo.
From the tool's definition Tool name includes 'edit' and description states 'table write-back before applying structural changes', indicating modification of document content.
Attacks that exploit this kind of access
Plan a DOCX table write-back before applying structural changes. It is categorised as a Write tool in the Asset Aware MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Asset Aware MCP server in PolicyLayer and add a rule for docx_table_edit_plan: 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 Asset Aware. Nothing to install.
docx_table_edit_plan 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 docx_table_edit_plan 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 docx_table_edit_plan. 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.
docx_table_edit_plan is provided by the Asset Aware MCP server (u9401066/asset-aware-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →