AI agents use create_document_post to create or update resources in LinkedIn Intelligence MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your LinkedIn Intelligence MCP Server environment.
This tool creates new content (a document post) on LinkedIn, which is a reversible write operation. The post can be deleted or edited after creation. While it could potentially be misused to spam or post misleading content at scale, the blast radius is limited to content creation without financial impact or irreversible data destruction.
From the tool's definition Tool name is 'create_document_post' which indicates creation of a post with document content on LinkedIn. The server description states it enables 'content creation and scheduling' on LinkedIn.
Documented attack patterns abuse exactly the kind of access create_document_post gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and LinkedIn Intelligence MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_document_post:
{
"version": "1",
"default": "deny",
"tools": {
"create_document_post": {
"limits": [
{
"counter": "create_document_post_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_document_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.
create_document_post. It is categorised as a Write tool in the LinkedIn Intelligence MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the LinkedIn Intelligence MCP Server MCP server in PolicyLayer and add a rule for create_document_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 Intelligence MCP Server. Nothing to install.
create_document_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 create_document_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 create_document_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.
create_document_post is provided by the LinkedIn Intelligence MCP Server MCP server (southleft/linkedin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 87 LinkedIn Intelligence MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
87 LinkedIn Intelligence MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.