linkedin_unlike_post
Remove a like (reaction) from a LinkedIn post
This record as markdown: /tools/io-github-alifanov-scopegate/linkedin-unlike-post.md
What linkedin_unlike_post does on ScopeGate
AI agents use linkedin_unlike_post to create or update resources in ScopeGate, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ScopeGate environment.
Why linkedin_unlike_post is rated Medium
This tool modifies data reversibly by removing a like/reaction. It is not destructive (the like can be re-added), not financial, and not a pure read operation since it changes state. It does not execute arbitrary code or trigger uncontrolled external effects.
From the tool's definition Tool name 'linkedin_unlike_post' and description 'Remove a like (reaction) from a LinkedIn post' indicate a modification action that changes the user's interaction state with LinkedIn content.
Attacks that exploit this kind of access
The rule that runs linkedin_unlike_post safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScopeGate, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For linkedin_unlike_post, this is the rule to start with:
linkedin_unlike_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.
The button opens the PolicyLayer dashboard: create your workspace, connect ScopeGate, apply this rule, and every linkedin_unlike_post call is checked against it from then on.
Questions about linkedin_unlike_post
Remove a like (reaction) from a LinkedIn post. It is categorised as a Write tool in the ScopeGate MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ScopeGate MCP server in PolicyLayer and add a rule for linkedin_unlike_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 ScopeGate. Nothing to install.
linkedin_unlike_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 linkedin_unlike_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 linkedin_unlike_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.
linkedin_unlike_post is provided by the ScopeGate MCP server (https://mcp.scopegate.cloud/{api_key}). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScopeGate, and thousands of servers like it.
This server
Across the catalogue