Set up deployment workflow for GitHub Pages or Vercel with deployment tracking and preference learning. Use the
AI agents invoke deploy_site to trigger actions in Documcp. 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.
This tool performs automated deployment workflows to GitHub Pages or Vercel, which are external execution operations that trigger publishing pipelines. While not destructive in the sense of deletion, it executes code/workflows whose effects depend on arguments and affects live production systems.
From the tool's definition Tool description states it will 'Set up deployment workflow for GitHub Pages or Vercel' — this involves triggering automated deployment operations and external system integrations that execute code/workflows to publish changes to live production environments.
Documented attack patterns abuse exactly the kind of access deploy_site gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Documcp, and nothing reaches the server without passing your rules. This is the rule we recommend for deploy_site:
{
"version": "1",
"default": "deny",
"tools": {
"deploy_site": {
"limits": [
{
"counter": "deploy_site_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}deploy_site 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.
Free to start. No card required.
Set up deployment workflow for GitHub Pages or Vercel with deployment tracking and preference learning. Use the. It is categorised as a Execute tool in the Documcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Docu MCP server in PolicyLayer and add a rule for deploy_site: 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 Documcp. Nothing to install.
deploy_site 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 deploy_site 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_site. 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_site is provided by the Docu MCP server (tosin2013/documcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Documcp, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
52 Documcp tools catalogued and risk-classified — across an index of 43,000+ MCP servers.