integration_setup
Inspect, list, or configure integrations directly from chat.
This record as markdown: /tools/cowork-os/integration-setup.md
What integration_setup does on CoWork OS
AI agents use integration_setup to create or update resources in CoWork OS, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CoWork OS environment.
Why integration_setup is rated Medium
The tool permits inspection and listing (Read operations) but also explicitly supports configuration of integrations, which modifies system state reversibly. Configuration changes are typically not permanent deletions and can be adjusted afterward, qualifying as Write rather than Destructive.
From the tool's definition Tool description states it can 'configure integrations directly from chat,' indicating modification of integration settings. The verb 'configure' denotes changes to system state, placing this in the Write category rather than Read.
Attacks that exploit this kind of access
The rule that runs integration_setup safely
PolicyLayer is an MCP gateway: it sits between your AI agents and CoWork OS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For integration_setup, this is the rule to start with:
integration_setup 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 CoWork OS, apply this rule, and every integration_setup call is checked against it from then on.
Questions about integration_setup
Inspect, list, or configure integrations directly from chat. It is categorised as a Write tool in the CoWork OS MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the CoWork OS MCP server in PolicyLayer and add a rule for integration_setup: 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 CoWork OS. Nothing to install.
integration_setup 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 integration_setup 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 integration_setup. 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.
integration_setup is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on CoWork OS, and thousands of servers like it.
This server
Across the catalogue