Skip to content
KiweelyKiweelyKiweely

Risk of Personal MCP Servers Pointed at a Client Workday Sandbox

Personal MCP servers on consultant laptops hold tokens and bypass central audit. Treat them as shadow gateways even against Sandbox.

  • By Kiweely
  • Updated
  • 1 min read
On this page

Workday documents enterprise Agent-Ready tool access through Agent System of Record and its MCP endpoint patterns for registered agents. A personal MCP server on a contractor laptop with a Sandbox refresh token is a different animal: unmanaged runtime, local logs, and unclear wipe on offboarding.

Risks

  • Tokens in local config files.
  • No central tool allowlist.
  • Sandbox data that still includes near-Production worker copies after refresh.
  • Drift when Workday releases change APIs twice a year.

Direction

Use customer-approved connectors and ASOR registration where required; ban personal always-on MCP processes with client credentials; wipe on offboarding.

Your Workday work, done by AI.

Kiweely Vine is the AI agent that builds, deploys and tests Extend apps as real people, makes changes in any Workday task screen, answers from your real tenant and builds reports.

Get the next one in your inbox.

One email a month for Workday teams: what’s changing in Workday and what to retest, one tip tried in a real tenant, and what’s new at Kiweely.

We’ll email you once to confirm. Unsubscribe in one click from any issue.