Export design nodes to PDF documents
AI agents use export_pdf to create or update resources in AI-Canvas MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AI-Canvas MCP Server environment.
Exporting to PDF creates a new file output based on design nodes, which is a write operation that generates data. While not destructive (the original design remains intact) and not immediately dangerous, it creates an artifact that could be misused (e.g., exporting sensitive designs without authorization, or generating files that bypass access controls).
From the tool's definition Tool name 'export_pdf' and description 'Export design nodes to PDF documents' indicate creation of a new file artifact (PDF) from existing design data.
Attacks that exploit this kind of access
Export design nodes to PDF documents. It is categorised as a Write tool in the AI-Canvas MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AI-Canvas MCP Server MCP server in PolicyLayer and add a rule for export_pdf: 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-Canvas MCP Server. Nothing to install.
export_pdf 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_pdf 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_pdf. 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_pdf is provided by the AI-Canvas MCP Server MCP server (laoluojuhai/ai-canvas). 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 →