connect_account · Unipile MCP: Risk & Policy

WHAT IT DOES

What connect_account does on Unipile

AI agents use connect_account to create or update resources in Unipile — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Unipile environment.

WHY IT NEEDS A POLICY

Why connect_account needs a policy

An AI agent can call connect_account faster than any human can review — one bad instruction and it creates or modifies resources in Unipile by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

connect_account Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "connect_account": {
      "limits": [
        {
          "counter": "connect_account_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Unipile, so you can run agents against it safely.

FAQ

Questions about connect_account

What does the connect_account tool do? +

connect_account. It is categorised as a Write tool in the Unipile MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on connect_account? +

Register the Unipile MCP server in PolicyLayer and add a rule for connect_account: 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 Unipile. Nothing to install.

What risk level is connect_account? +

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

Can I rate-limit connect_account? +

Yes. Add a rate_limit block to the connect_account 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 connect_account completely? +

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

connect_account is provided by the Unipile MCP server (sundeepg98/mcp-server-unipile). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.