env.sync

// WHEN AI AGENTS USE THIS TOOL

AI agents use env.sync to create or modify resources in Autodock. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

// WHY ENFORCE A POLICY ON ENV.SYNC

Without a policy, an AI agent could call env.sync repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Autodock.

// RECOMMENDED POLICY

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

mikesol-autodock.yaml

tools:
  env.sync:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Autodock policy for all 27 tools.

// DETAILS

Tool Name env.sync

Category Write

MCP Server Autodock MCP Server

Risk Level Medium

// MORE AUTODOCK TOOLS

Destructive account.revoke_api_key Destructive env.destroy Destructive env.unexpose Execute browser.listen Execute env.email Execute env.expose Execute env.gh_runner Execute env.restart

View all 27 tools →

// WHAT CAN GO WRONG

Agents calling write-class tools like env.sync have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER WRITE TOOLS ACROSS MCP SERVERS

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

AbraFlexi contact_create AbraFlexi contact_update AbraFlexi evidence_create AbraFlexi evidence_update AbraFlexi invoice_issued_update AbraFlexi invoice_received_create

// RELATED READING

// FAQ

What does the env.sync tool do? +

REQUIRED before syncing files to an Autodock environment. Provides SSH connection details and rsync templates. Does NOT perform the sync itself. If environmentId omitted, auto-selects when exactly one running env exists. CRITICAL: .ENV FILE HANDLING (the #1 source of remote dev issues) Local .env files contain localhost URLs that MUST be patched for remote development. Do NOT rsync .env files blindly - handle them specially. WORKFLOW: 1. SCAN: grep -r "localhost" .env* to find URLs needing patches 2. CLASSIFY each variable as EXTERNAL (browser/user-facing) or INTERNAL (machine-to-machine) 3. PATCH external URLs to https://<port>--<slug>.autodock.io 4. COPY patched .env to remote separately from main rsync 5. PRESERVE: keep .env.local.original on remote to detect local changes on re-sync EXTERNAL VARS (patch to autodock URL): NEXT_PUBLIC_*, VITE_*, REACT_APP_* (browser-accessible) API_URL, BACKEND_URL, FRONTEND_URL, APP_URL, BASE_URL, NEXTAUTH_URL CSRF_TRUSTED_ORIGINS, ALLOWED_HOSTS, CORS_ALLOWED_ORIGINS WS_URL, WEBSOCKET_URL (use wss:// instead of https://) OAUTH_REDIRECT_URI, CALLBACK_URL INTERNAL VARS (keep as localhost): DATABASE_URL, DB_HOST, POSTGRES_*, MYSQL_*, REDIS_*, MONGODB_*, CACHE_URL ELASTICSEARCH_URL, RABBITMQ_URL, KAFKA_*, *_SERVICE_HOST EXAMPLE: Local: NEXT_PUBLIC_API_URL=http://localhost:3001 Remote (after exposing 3001): NEXT_PUBLIC_API_URL=https://3001--my-env.autodock.io SHADOW COPY: On first sync, save .env.local.original. On re-sync, compare local to .env.local.original - only re-patch if local changed (preserves remote patches).. It is categorised as a Write tool in the Autodock MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on env.sync? +

Add a rule in your Intercept YAML policy under the tools section for env.sync. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Autodock MCP server.

What risk level is env.sync? +

env.sync is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit env.sync? +

Yes. Add a rate_limit block to the env.sync rule in your Intercept 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 env.sync completely? +

Set action: deny in the Intercept policy for env.sync. 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 env.sync? +

env.sync is provided by the Autodock MCP server (mikesol/autodock). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Autodock