gts_report_remote
Send a moderation report to a remote server about one of their accounts.
This record as markdown: /tools/kh0pper-crow/gts-report-remote.md
What gts_report_remote does on Crow
AI agents use gts_report_remote 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.
Why gts_report_remote is rated Medium
This tool creates a new moderation report on a remote server, which is a reversible write operation. It does not execute arbitrary code or scripts (Execute), delete data (Destructive), move money (Financial), or retrieve data without side effects (Read).
From the tool's definition Tool description states 'Send a moderation report to a remote server about one of their accounts.' The verb 'Send' and action of submitting a report to a remote system indicates creation/modification of data (the report) on another system.
Attacks that exploit this kind of access
The rule that runs gts_report_remote 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_report_remote, this is the rule to start with:
gts_report_remote 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 Crow, apply this rule, and every gts_report_remote call is checked against it from then on.
Questions about gts_report_remote
Send a moderation report to a remote server about one of their accounts. 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_report_remote: 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_report_remote 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_report_remote 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_report_remote. 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_report_remote 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