AI agents use linkedin_events_create to create or update resources in Linkedin — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Linkedin environment.
This tool creates a new LinkedIn event, which is a reversible Write operation. It modifies state by adding new data to the platform but does not execute arbitrary code, delete data, or involve financial transactions. The severity is medium because creating events could spam users or be used for misleading campaigns, but the action is reversible (events can be deleted/cancelled).
From the tool's definition Tool name 'linkedin_events_create' and description 'Create LinkedIn event' indicate creation of new content/data on LinkedIn platform.
Attacks that exploit this kind of access
Create LinkedIn event. It is categorised as a Write tool in the Linkedin MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Linkedin MCP server in PolicyLayer and add a rule for linkedin_events_create: 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. Nothing to install.
linkedin_events_create 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 linkedin_events_create 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 linkedin_events_create. 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.
linkedin_events_create is provided by the Linkedin MCP server (maheidem/linkedin-optimizer-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →