Low Risk

gts_feed

Fetch a timeline. Choices: home (authenticated user

How to control gts_feed ↓

What gts_feed does on Crow

AI agents call gts_feed to retrieve information from Crow without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why gts_feed needs a policy

This tool retrieves timeline data for display purposes only. 'Fetch' is a classic read operation that queries and returns data without modifying, deleting, or executing any external operations. The capability is limited to data retrieval from what appears to be a GoToSocial (GTS) server integration.

From the tool's definition Tool name 'gts_feed' with description 'Fetch a timeline' indicates retrieval of data. The 'home' option references fetching an authenticated user's home timeline, which is a read-only query operation with no side effects.

Documented attack patterns abuse exactly the kind of access gts_feed gives an agent:

How to control gts_feed

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_feed:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "gts_feed": {}
  }
}

gts_feed is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Crow — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about gts_feed

What does the gts_feed tool do? +

Fetch a timeline. Choices: home (authenticated user. It is categorised as a Read tool in the Crow MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on gts_feed? +

Register the Crow MCP server in PolicyLayer and add a rule for gts_feed: 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.

What risk level is gts_feed? +

gts_feed is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit gts_feed? +

Yes. Add a rate_limit block to the gts_feed 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.

How do I block gts_feed completely? +

Set action: deny in the PolicyLayer policy for gts_feed. 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.

What MCP server provides gts_feed? +

gts_feed 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.

Enforce policy on every Crow tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.