structured_doc
Create and edit structured documents (quotations, invoices, proposals) via JSON-DSL templates + @react-pdf/renderer. Pattern: TEMPLATE (curated, shared library, JSON tree of {type, style, children}) + DATA (JSON filled by you, privado al agente/usuario). You NEVER write layout — templates handle ...
This record as markdown: /tools/cloud-easybits-easybits/structured-doc.md
What structured_doc does on EasyBits
AI agents use structured_doc to create or update resources in EasyBits, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your EasyBits environment.
Why structured_doc is rated Medium
Creates and modifies business documents reversibly using templates and JSON data.
From the tool's definition Create and edit structured documents (quotations, invoices, proposals)
Attacks that exploit this kind of access
The rule that runs structured_doc safely
PolicyLayer is an MCP gateway: it sits between your AI agents and EasyBits, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For structured_doc, this is the rule to start with:
structured_doc stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect EasyBits, apply this rule, and every structured_doc call is checked against it from then on.
Questions about structured_doc
Create and edit structured documents (quotations, invoices, proposals) via JSON-DSL templates + @react-pdf/renderer. Pattern: TEMPLATE (curated, shared library, JSON tree of {type, style, children}) + DATA (JSON filled by you, privado al agente/usuario). You NEVER write layout — templates handle that. You only produce the data object that the template consumes. Actions: - list_templates: List available templates (yours + public). Returns [{id, name, description, dataSchema}]. - get_template: { templateId } → { id, name, tree, dataSchema }. Verbose: includes full tree. Prefer get_template_schema when you only need the schema. - get_template_schema: { templateId } → { id, name, description, dataSchema }. Lightweight variant that skips tree — use this when you just need the field list to build the data object. - create_template: { name, description?, tree, dataSchema, isPublic? } → { templateId }. Create a reusable template. It is categorised as a Write tool in the EasyBits MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the EasyBits MCP server in PolicyLayer and add a rule for structured_doc: 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 EasyBits. Nothing to install.
structured_doc 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 structured_doc 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 structured_doc. 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.
structured_doc is provided by the EasyBits MCP server (@easybits.cloud/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on EasyBits, and thousands of servers like it.
This server
Across the catalogue