AI agents call export_final_document to retrieve information from AI Develop Assistant without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool 'exports' a document, which is fundamentally a read/retrieval operation — it compiles and outputs existing requirements and architecture data into a document. No modification, execution, or deletion is implied. Severity is low since misuse would at most expose project documentation.
From the tool's definition 导出完整的项目需求和架构文档 (Export complete project requirements and architecture documents)
Documented attack patterns abuse exactly the kind of access export_final_document gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AI Develop Assistant, and nothing reaches the server without passing your rules. This is the rule we recommend for export_final_document:
{
"version": "1",
"default": "deny",
"tools": {
"export_final_document": {}
}
}export_final_document is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
导出完整的项目需求和架构文档. It is categorised as a Read tool in the AI Develop Assistant MCP Server, which means it retrieves data without modifying state.
Register the AI Develop Assistant MCP server in PolicyLayer and add a rule for export_final_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 AI Develop Assistant. Nothing to install.
export_final_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 export_final_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 export_final_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.
export_final_document is provided by the AI Develop Assistant MCP server (jiemobasixiangcai/ai-develop-assistant). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AI Develop Assistant, 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.
5 AI Develop Assistant tools catalogued and risk-classified — across an index of 43,000+ MCP servers.