AI agents use unlike-post to create or update resources in Bluesky — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bluesky environment.
This tool modifies engagement state on the Bluesky platform by removing a like, which is a reversible change to data. It does not delete the post itself, execute arbitrary code, move money, or cause irreversible damage.
From the tool's definition Tool name 'unlike-post' and description 'Remove your like from a post' indicate a modification operation that removes a like engagement from a post on Bluesky.
Documented attack patterns abuse exactly the kind of access unlike-post gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Bluesky, and nothing reaches the server without passing your rules. This is the rule we recommend for unlike-post:
{
"version": "1",
"default": "deny",
"tools": {
"unlike-post": {
"limits": [
{
"counter": "unlike-post_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
Remove your like from a post. It is categorised as a Write tool in the Bluesky MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Bluesky MCP server in PolicyLayer and add a rule for 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 Bluesky. Nothing to install.
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 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 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.
unlike-post is provided by the Bluesky MCP server (semioz/bluesky-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Bluesky, 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.
11 Bluesky tools catalogued and risk-classified — across an index of 43,000+ MCP servers.