send_linkedin_message
AI agents invoke send_linkedin_message to trigger actions in Multilead Open API MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Sending a LinkedIn message triggers an external operation (delivering a message to another user on the LinkedIn platform), which is an irreversible outbound action. This falls under Execute as it triggers an external operation. Severity is high because an AI agent could misuse this to send unsolicited or harmful messages to contacts at scale. Confidence is reduced due to the empty description.
From the tool's definition Tool name 'send_linkedin_message'; description is empty and uninformative.
Attacks that exploit this kind of access
send_linkedin_message. It is categorised as a Execute tool in the Multilead Open API MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Multilead Open API MCP Server MCP server in PolicyLayer and add a rule for send_linkedin_message: 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 Multilead Open API MCP Server. Nothing to install.
send_linkedin_message is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the send_linkedin_message 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 send_linkedin_message. 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.
send_linkedin_message is provided by the Multilead Open API MCP Server MCP server (vanman2024/multilead-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 →