create_connect_session · Posterly MCP: Risk & Policy

WHAT IT DOES

What create_connect_session does on Posterly

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

WHY IT NEEDS A POLICY

Why create_connect_session needs a policy

This tool creates and modifies session state to establish new social media account connections. While it does not delete data or move money, it does create reversible integrations and authentication artifacts. The 'handoff session' mechanism represents a write-level side effect that establishes new connections in the Posterly system.

From the tool's definition Tool description explicitly states 'Create a short-lived Posterly dashboard handoff session for connecting a social account' and instructs to 'Send the secure connection URL to the user', indicating it creates session artifacts and initiates account linking…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_connect_session Rate-limited

create_connect_session 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": {
    "create_connect_session": {
      "limits": [
        {
          "counter": "create_connect_session_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 Posterly, so you can run agents against it safely.

FAQ

Questions about create_connect_session

What does the create_connect_session tool do? +

Create a short-lived Posterly dashboard handoff session for connecting a social account. Send the secure connection URL to the user, then poll get_connect_session to narrate progress. Do not ask for social media passwords or OAuth codes; Posterly handles those browser steps. It is categorised as a Write tool in the Posterly MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_connect_session? +

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

What risk level is create_connect_session? +

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

Can I rate-limit create_connect_session? +

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

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

create_connect_session is provided by the Posterly MCP server (posterly-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.