AI agents use share_linkedin_post to create or update resources in LinkedIn MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your LinkedIn MCP Server environment.
This tool creates new data (a LinkedIn post) that is reversible (posts can be deleted). It modifies a user's LinkedIn profile state by adding public content, but does not execute arbitrary code, delete data irreversibly, or move money. The blast radius is moderate—an AI agent misusing this could spam, post misleading information, or damage professional reputation, but the action can be undone.
From the tool's definition Tool name 'share_linkedin_post' and description 'Share a new post on LinkedIn' indicate creation of new content on a social media platform.
Documented attack patterns abuse exactly the kind of access share_linkedin_post gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and LinkedIn MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for share_linkedin_post:
{
"version": "1",
"default": "deny",
"tools": {
"share_linkedin_post": {
"limits": [
{
"counter": "share_linkedin_post_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}share_linkedin_post 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.
Free to start. No card required.
Share a new post on LinkedIn. It is categorised as a Write tool in the LinkedIn MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the LinkedIn MCP Server MCP server in PolicyLayer and add a rule for share_linkedin_post: 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 LinkedIn MCP Server. Nothing to install.
share_linkedin_post 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 share_linkedin_post 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 share_linkedin_post. 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.
share_linkedin_post is provided by the LinkedIn MCP Server MCP server (quinnjr/linkedin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from LinkedIn MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
18 LinkedIn MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.