seo__search_operators

［搜尋引擎與 AI 爬蟲工具箱］搜尋指令（site:、filetype:、intitle:、before: 等）在 Google、Bing、Yahoo、百度的支援對照與已失效指令。

SERVERAI 代理人任務中樞 SOURCEhttps://hub.penguindriver.com/mcp

Low RISK CLASS

Category Read

Parameters 10 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/com-penguindriver-hub/seo--search-operators.md

WHAT IT DOES

What seo__search_operators does on AI 代理人任務中樞

AI agents call seo__search_operators to retrieve information from AI 代理人任務中樞 without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`engine`	string	—

Parameters from the server's own tool schema.

RISK

Why seo__search_operators is rated Low

Even though seo__search_operators only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs seo__search_operators safely

PolicyLayer is an MCP gateway: it sits between your AI agents and AI 代理人任務中樞, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For seo__search_operators, this is the rule to start with:

seo__search_operators Allowed

seo__search_operators 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": {
    "seo__search_operators": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect AI 代理人任務中樞, apply this rule, and every seo__search_operators call is checked against it from then on.

FAQ

Questions about seo__search_operators

What does the seo__search_operators tool do? +

［搜尋引擎與 AI 爬蟲工具箱］搜尋指令（site:、filetype:、intitle:、before: 等）在 Google、Bing、Yahoo、百度的支援對照與已失效指令。. It is categorised as a Read tool in the AI 代理人任務中樞 MCP Server, which means it retrieves data without modifying state.

What parameters does seo__search_operators accept? +

seo__search_operators accepts 1 parameter: engine. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on seo__search_operators? +

Register the AI 代理人任務中樞 MCP server in PolicyLayer and add a rule for seo__search_operators: 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 AI 代理人任務中樞. Nothing to install.

What risk level is seo__search_operators? +

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

Can I rate-limit seo__search_operators? +

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

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

seo__search_operators is provided by the AI 代理人任務中樞 MCP server (https://hub.penguindriver.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on AI 代理人任務中樞, and thousands of servers like it.

This server

All 174 AI 代理人任務中樞 tools →

Across the catalogue

binary_search on 010 Editor →evaluate_search_quality on ACE-MCP →search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server → The MCP Attack Database →

Guides

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