AI agents use export_structure to create or update resources in Doc — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Doc environment.
This tool creates/generates structured output files (JSON or Markdown) from document analysis. While it doesn't modify existing data irreversibly, it does write/create new files which constitutes a Write operation. Severity is medium because file exports could potentially consume storage or overwrite existing files if not properly handled, but the operation is typically reversible.
From the tool's definition Tool name 'export_structure' with description 'Export document structure as JSON or Markdown file' indicates creation or generation of new files/exports. The verb 'export' combined with 'to JSON or Markdown file' suggests the tool writes output data to files.
Attacks that exploit this kind of access
导出文档结构为JSON或Markdown文件. It is categorised as a Write tool in the Doc MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Doc MCP server in PolicyLayer and add a rule for export_structure: 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 Doc. Nothing to install.
export_structure 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 export_structure 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 export_structure. 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.
export_structure is provided by the Doc MCP server (jiahuidegit/doc-mcp-server). 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 →