seo__build_search_urls
[搜尋引擎與 AI 爬蟲工具箱]一次產生 Google、Bing、Yahoo 奇摩、百度、YouTube 的進階搜尋網址(關鍵字、完全符合、排除字、限定網站、檔案類型、時間)。
This record as markdown: /tools/com-penguindriver-hub/seo--build-search-urls.md
What seo__build_search_urls does on AI 代理人任務中樞
AI agents invoke seo__build_search_urls to trigger actions in AI 代理人任務中樞. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
q | string | Yes | |
site | string | — | |
time | string | — | |
exact | string | — | |
exclude | string | — | |
filetype | string | — |
Parameters from the server's own tool schema.
Why seo__build_search_urls is rated High
seo__build_search_urls triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
The rule that runs seo__build_search_urls 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__build_search_urls, this is the rule to start with:
seo__build_search_urls stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect AI 代理人任務中樞, apply this rule, and every seo__build_search_urls call is checked against it from then on.
Questions about seo__build_search_urls
[搜尋引擎與 AI 爬蟲工具箱]一次產生 Google、Bing、Yahoo 奇摩、百度、YouTube 的進階搜尋網址(關鍵字、完全符合、排除字、限定網站、檔案類型、時間)。. It is categorised as a Execute tool in the AI 代理人任務中樞 MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
seo__build_search_urls accepts 6 parameters: q, site, time, exact, exclude, filetype. Required: q. The full parameter table on this page comes from the server's own tool schema.
Register the AI 代理人任務中樞 MCP server in PolicyLayer and add a rule for seo__build_search_urls: 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.
seo__build_search_urls is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the seo__build_search_urls 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 seo__build_search_urls. 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.
seo__build_search_urls 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.
More on AI 代理人任務中樞, and thousands of servers like it.
Across the catalogue