Follow an account by handle (@user@domain) or local account ID. Rate-limited: 30/hour.
AI agents use gts_follow to create or update resources in Crow — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Crow environment.
Following an account creates a new relationship/subscription on a social platform (GoToSocial). This is a reversible write action (can be unfollowed), but misuse could spam follow requests or expose the AI agent's social graph. Severity is medium due to the social/reputational impact and rate-limiting suggesting potential for abuse.
From the tool's definition Follow an account by handle (@user@domain) or local account ID
Documented attack patterns abuse exactly the kind of access gts_follow gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Crow, and nothing reaches the server without passing your rules. This is the rule we recommend for gts_follow:
{
"version": "1",
"default": "deny",
"tools": {
"gts_follow": {
"limits": [
{
"counter": "gts_follow_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} gts_follow 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.
Follow an account by handle (@user@domain) or local account ID. Rate-limited: 30/hour. It is categorised as a Write tool in the Crow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Crow MCP server in PolicyLayer and add a rule for gts_follow: 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 Crow. Nothing to install.
gts_follow 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 gts_follow 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 gts_follow. 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.
gts_follow is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Crow, 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.
576 Crow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.