pt_search

Search videos + channels across local + cached federated content. Rate-limited: 60/hour.

SERVERCrow SOURCEkh0pper/crow

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/kh0pper-crow/pt-search.md

WHAT IT DOES

What pt_search does on Crow

AI agents call pt_search 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.

RISK

Why pt_search is rated Low

This tool performs a search operation across video and channel data, which is fundamentally a read-only operation that retrieves information without side effects. The rate-limiting (60/hour) further confirms it is designed as a safe query operation. No data is created, modified, deleted, executed, or involves financial operations.

From the tool's definition Tool name 'pt_search' and description 'Search videos + channels across local + cached federated content' indicate retrieval/query of existing data with no modification or execution capability.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs pt_search 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 pt_search, this is the rule to start with:

pt_search Allowed

pt_search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pt_search": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Crow, apply this rule, and every pt_search call is checked against it from then on.

FAQ

Questions about pt_search

What does the pt_search tool do? +

Search videos + channels across local + cached federated content. Rate-limited: 60/hour. 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 pt_search? +

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

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

Can I rate-limit pt_search? +

Yes. Add a rate_limit block to the pt_search 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 pt_search completely? +

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

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

KEEP EXPLORING

More on Crow, and thousands of servers like it.

This server

All 587 Crow tools →

Across the catalogue

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →hybrid_search on Azure AI Agent Service + Azure AI Search MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →