build_xlsx_workbook
pdfpeek: Build a styled Excel workbook from JSON sheets, columns and rows. To read a workbook back use convert_excel_to_json; for slides use build_pptx_deck. Rows are arrays or objects; a column type (string, number, integer, date, datetime, boolean, currency, percent) sets the format. Strings ar...
This record as markdown: /tools/dev-tanod-tanod/build-xlsx-workbook.md
What build_xlsx_workbook does on Tanod
AI agents invoke build_xlsx_workbook to trigger actions in Tanod. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
output | string | — | base64 (default): inline. url: stored for 24 hours; link, metadata. |
sheets | array | Yes | The sheets, in order: 1-20, each with a unique name, optional typed columns and rows (at most 50,000 cells in all). |
filename | object | — | Name of the returned file (default workbook.xlsx; .xlsx is added when missing; only letters, digits, space, dot, dash and underscore are kept). |
Parameters from the server's own tool schema.
Why build_xlsx_workbook is rated High
build_xlsx_workbook triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Risk signalsAccepts file system path (filename)
Attacks that exploit this kind of access
The rule that runs build_xlsx_workbook safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tanod, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For build_xlsx_workbook, this is the rule to start with:
build_xlsx_workbook stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Tanod, apply this rule, and every build_xlsx_workbook call is checked against it from then on.
Questions about build_xlsx_workbook
pdfpeek: Build a styled Excel workbook from JSON sheets, columns and rows. To read a workbook back use convert_excel_to_json; for slides use build_pptx_deck. Rows are arrays or objects; a column type (string, number, integer, date, datetime, boolean, currency, percent) sets the format. Strings are always stored as text, never as formulas. At most 20 sheets, 50,000 cells, 32,767 characters per cell; sheet names of at most 31 characters without [ ] : * ? / \. Over a limit is a 422 (not charged). Typically under 1 s. Price: USD 0.005. No free tier. Docs: https://tanod.dev/learn/xlsx-build-api.html. It is categorised as a Execute tool in the Tanod MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
build_xlsx_workbook accepts 3 parameters: output, sheets, filename. Required: sheets. The full parameter table on this page comes from the server's own tool schema.
Register the Tanod MCP server in PolicyLayer and add a rule for build_xlsx_workbook: 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 Tanod. Nothing to install.
build_xlsx_workbook is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the build_xlsx_workbook 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 build_xlsx_workbook. 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.
build_xlsx_workbook is provided by the Tanod MCP server (https://tanod.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Tanod, and thousands of servers like it.
Across the catalogue