Send a moderation report to a remote server about one of their accounts.
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.
This tool creates/submits new data (a moderation report) to a remote server, which is a write operation. While it could theoretically cause reputational harm to the reported account, the action is not irreversible (reports can be appealed, dismissed, or withdrawn), and the primary function is data creation rather than destruction or code execution.
From the tool's definition Tool performs 'Send a moderation report' which creates new data (a report record) on a remote system. The action is reversible in principle (reports can be withdrawn or marked as resolved), and does not delete data, execute arbitrary code, or move financial…
Documented attack patterns abuse exactly the kind of access gts_report_remote 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_report_remote:
{
"version": "1",
"default": "deny",
"tools": {
"gts_report_remote": {
"limits": [
{
"counter": "gts_report_remote_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
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.
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.