How to Give an AI Agent Safe Access to Your LinkedIn
An assistant that can post on your company page is a real risk if you set it up carelessly. MediaPilot splits access into four separate permissions so you can hand over exactly as much as you mean to — and take it back in one click.
Understand the four permissions
Read lets the assistant see posts, topics, comments, analytics and the credit balance. Draft lets it write and edit drafts. Schedule lets it put a post in the queue. Publish lets it post to LinkedIn immediately. They are granted separately, and a connection without publish can never post, however the assistant is prompted.
Start smaller than you think you need
Read and draft cover most of the value: the assistant researches, writes and prepares, and you publish. Add scheduling once the drafts are consistently good, and publishing only if you genuinely want posts going out unattended.
Pick the workspaces deliberately
On the permission screen you choose which workspaces the connection may reach. An agency can grant several to one connector; a client workspace you did not tick stays invisible to it, even if you are a member.
Keep one connection per assistant
Separate connections mean you can revoke one without breaking the others, and the audit log tells you which assistant did what.
Check the log
Every MCP call is recorded with the workspace, the tool and the time. If a post appears that you do not recognise, the log says which connection created it.
Revoke when you are done
Remove a connection in MediaPilot under Account → MCP and it stops working immediately — its tokens are dead, not merely expired. Do this when you stop using an assistant, and whenever a device you used it on is lost.