Like / dislike / unrate a video by numeric id. Rate-limited: 60/hour.
AI agents use pt_rate_video 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 writes a rating (like/dislike/unrate) to an external video platform. It modifies data reversibly (ratings can be changed or removed), so it falls under Write. Misuse could spam ratings on videos at scale (up to 60/hour), but it does not delete data or move money, making severity medium.
From the tool's definition Like / dislike / unrate a video by numeric id
Documented attack patterns abuse exactly the kind of access pt_rate_video 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 pt_rate_video:
{
"version": "1",
"default": "deny",
"tools": {
"pt_rate_video": {
"limits": [
{
"counter": "pt_rate_video_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} pt_rate_video 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.
Like / dislike / unrate a video by numeric id. Rate-limited: 60/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 pt_rate_video: 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.
pt_rate_video 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 pt_rate_video 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 pt_rate_video. 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.
pt_rate_video 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.