deploy_document
Publish a document as a live website at www.easybits.cloud/s/{slug}/ — instant hosting, shareable link. Requires at least one page/section.
This record as markdown: /tools/cloud-easybits-easybits/deploy-document.md
What deploy_document does on EasyBits
AI agents use deploy_document 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 deploy_document is rated Medium
Creates and publishes a publicly accessible website, a reversible write operation.
From the tool's definition Publish a document as a live website, instant hosting, shareable link
Attacks that exploit this kind of access
The rule that runs deploy_document 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 deploy_document, this is the rule to start with:
deploy_document 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 deploy_document call is checked against it from then on.
Questions about deploy_document
Publish a document as a live website at www.easybits.cloud/s/{slug}/ — instant hosting, shareable link. Requires at least one page/section. 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 deploy_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 EasyBits. Nothing to install.
deploy_document 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 deploy_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 deploy_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.
deploy_document 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