ingest_docx
AI agents use ingest_docx 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.
'Ingest' typically means reading a file and storing/indexing it in the system, which is a Write operation (creating new data in the knowledge graph or document store). The empty description lowers confidence. Given sibling tools like 'delete_document' and 'convert_document', this server manages documents, so ingest likely means uploading/importing a DOCX file — a reversible Write action.
From the tool's definition Tool name 'ingest_docx' suggests ingesting/importing a DOCX file into the system, implying data is written or created. Description is empty, providing no additional context.
Attacks that exploit this kind of access
ingest_docx. 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 ingest_docx: 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.
ingest_docx 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 ingest_docx 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 ingest_docx. 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.
ingest_docx 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 →