デザインIDとパラメータを指定してPDFを生成します。応答にダウンロード URL が含まれるため、本ツール 1 回の呼び出しで結果提示が完結します (別途ダウンロード用ツールを呼ぶ必要はありません)。 - stdio モード (Claude Desktop / Code): ローカルに保存し絶対パスも返します。outputDir で保存先を指定できます (未指定時はクライアントのワークスペース Roots または OS 一時ディレクトリ)。 - HTTP モード (claude.ai / n8n 等): サーバー側には保存せず、ダウンロード URL (fileUrl) と request...
Risk signalsAccepts raw HTML/template content (content) · Accepts file system path (content.fileName)
Part of the ReportFlow server.
Free to start. No card required.
AI agents use generate_pdf_sync to create or modify resources in ReportFlow. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call generate_pdf_sync repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach ReportFlow.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"generate_pdf_sync": {
"limits": [
{
"counter": "generate_pdf_sync_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full ReportFlow policy for all 5 tools.
These attack patterns abuse exactly the kind of access generate_pdf_sync gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
デザインIDとパラメータを指定してPDFを生成します。応答にダウンロード URL が含まれるため、本ツール 1 回の呼び出しで結果提示が完結します (別途ダウンロード用ツールを呼ぶ必要はありません)。 - stdio モード (Claude Desktop / Code): ローカルに保存し絶対パスも返します。outputDir で保存先を指定できます (未指定時はクライアントのワークスペース Roots または OS 一時ディレクトリ)。 - HTTP モード (claude.ai / n8n 等): サーバー側には保存せず、ダウンロード URL (fileUrl) と requestId / fileId を返します。 【重要】呼び出し前に必ず get_design_parameters でデザインの必要パラメータ構造を確認し、ユーザーから必要な値を聞き出すこと。プレースホルダー値・架空の値を勝手に生成しないこと。. It is categorised as a Write tool in the ReportFlow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ReportFlow MCP server in PolicyLayer and add a rule for generate_pdf_sync: 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 ReportFlow. Nothing to install.
generate_pdf_sync 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 generate_pdf_sync 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 generate_pdf_sync. 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.
generate_pdf_sync is provided by the ReportFlow MCP server (reportflow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 5 ReportFlow tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.