connect_workspace
Connect your Adrata workspace via OAuth 2.0. Opens a browser window for authorization. By default the connection is READ-ONLY (least privilege): search/read companies, people, opportunities, pipeline, buyer groups, signals and analytics, plus the governed AI dispatcher for reads. Pass writeAccess...
This record as markdown: /tools/adrata-starfield-mcp/connect-workspace.md
What connect_workspace does on Starfield
AI agents use connect_workspace to create or update resources in Starfield, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Starfield environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
writeAccess | boolean | — | Request CRM write scopes in addition to read. Defaults to false (read-only). |
Parameters from the server's own tool schema.
Why connect_workspace is rated Medium
An AI agent can call connect_workspace faster than any human can review: one bad instruction and it creates or modifies resources in Starfield by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs connect_workspace safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Starfield, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For connect_workspace, this is the rule to start with:
connect_workspace 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 Starfield, apply this rule, and every connect_workspace call is checked against it from then on.
Questions about connect_workspace
Connect your Adrata workspace via OAuth 2.0. Opens a browser window for authorization. By default the connection is READ-ONLY (least privilege): search/read companies, people, opportunities, pipeline, buyer groups, signals and analytics, plus the governed AI dispatcher for reads. Pass writeAccess:true to additionally request the CRM write scopes (companies, people, buyer groups, opportunities, actions, tasks) so create/update/delete work from this client; you will see them on the consent screen and can decline. Workspace administration and enrichment spend are never requested and always require a signed-in human session. The capability summary returned is derived from the scope the server actually granted, not from what was requested. It is categorised as a Write tool in the Starfield MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
connect_workspace accepts 1 parameter: writeAccess. The full parameter table on this page comes from the server's own tool schema.
Register the Starfield MCP server in PolicyLayer and add a rule for connect_workspace: 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 Starfield. Nothing to install.
connect_workspace 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 connect_workspace 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 connect_workspace. 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.
connect_workspace is provided by the Starfield MCP server (@adrata/starfield-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Starfield, and thousands of servers like it.
This server
Across the catalogue