This record as markdown: /tools/kh0pper-crow/gts-feed.md
What gts_feed does on Crow
AI agents call gts_feed to retrieve information from Crow without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why gts_feed is rated Low
The tool fetches timeline data (likely from GoToSocial based on 'gts' prefix), which is a read-only operation that retrieves existing information. The 'Fetch' verb and 'timeline' context confirm this is a query operation with no destructive, financial, or execution capabilities. Severity is low as data retrieval has minimal blast radius compared to write, execute, or destructive operations.
From the tool's definition Tool name 'gts_feed' and description 'Fetch a timeline' explicitly indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs gts_feed safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gts_feed, this is the rule to start with:
gts_feed is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Crow, apply this rule, and every gts_feed call is checked against it from then on.
Questions about gts_feed
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.
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.
gts_feed is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
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.
More on Crow, and thousands of servers like it.
This server
Across the catalogue