deploy_pages

THE RISK

High Risk

Why deploy_pages needs a policy

This tool executes a deployment workflow which runs code/operations against GitHub Pages infrastructure. Even though deprecated, it remains capable of triggering automated deployment actions whose effects depend on the repository context and cannot be easily reversed without additional administrative actions.

From the tool's definition 'Set up GitHub Pages deployment workflow' - this triggers automated deployment operations with external effects on GitHub infrastructure that depend on arguments and repository configuration.

Documented attack patterns abuse exactly the kind of access deploy_pages gives an agent:

POLICY

How to control deploy_pages

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_pages:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "deploy_pages": {
      "limits": [
        {
          "counter": "deploy_pages_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

deploy_pages 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.

Create a free account and register Documcp — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Documcp tools

Destructive cleanup_agent_artifacts Detect, classify, and clean up artifacts generated by AI coding agents (e.g., TODO.md, PLA Destructive memory_cleanup Clean up old memories Destructive memory_pruning Intelligent memory pruning and optimization Execute change_watcher Watch code changes and trigger documentation drift detection in near real-time. Execute deploy_site Set up deployment workflow for GitHub Pages or Vercel with deployment tracking and prefere Execute memory_migration Create and execute migration plans between different memory systems Execute test_local_deployment Test documentation build and local server before deploying to GitHub Pages Write optimize_readme Optimize README content by restructuring, condensing, and extracting detailed sections to

All 52 Documcp tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Documcp → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about deploy_pages

What does the deploy_pages tool do? +

[DEPRECATED — use deploy_site instead] Set up GitHub Pages deployment workflow. This alias will be removed in v1.1.0. 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.

How do I enforce a policy on deploy_pages? +

Register the Docu MCP server in PolicyLayer and add a rule for deploy_pages: 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.

What risk level is deploy_pages? +

deploy_pages is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit deploy_pages? +

Yes. Add a rate_limit block to the deploy_pages 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.

How do I block deploy_pages completely? +

Set action: deny in the PolicyLayer policy for deploy_pages. 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.

What MCP server provides deploy_pages? +

deploy_pages 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.

Enforce policy on every Documcp tool call.

Start from Documcp, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →