gsc_search_analytics
검색 성과 데이터 조회 (클릭·노출·CTR·평균순위). dimensions로 query/page/country/device/date/searchAppearance 별 분해. 요약(가중 평균순위 포함) + rows 반환.
This record as markdown: /tools/yoonion-mimi-seed-mcp/gsc-search-analytics.md
What gsc_search_analytics does on Mimi Seed
AI agents call gsc_search_analytics to retrieve information from Mimi Seed without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why gsc_search_analytics is rated Low
This tool queries and retrieves Google Search Console analytics data with various dimensions (query, page, country, device, date, searchAppearance). It returns summarized analytics and rows without modifying, deleting, or executing any operations. This is a pure data retrieval operation with no side effects, fitting the Read category.
From the tool's definition Tool name contains 'search_analytics' and description states it performs '검색 성과 데이터 조회' (search performance data retrieval) with retrieval of metrics like clicks, impressions, CTR, and average ranking.
Attacks that exploit this kind of access
The rule that runs gsc_search_analytics safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mimi Seed, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gsc_search_analytics, this is the rule to start with:
gsc_search_analytics is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mimi Seed, apply this rule, and every gsc_search_analytics call is checked against it from then on.
Questions about gsc_search_analytics
검색 성과 데이터 조회 (클릭·노출·CTR·평균순위). dimensions로 query/page/country/device/date/searchAppearance 별 분해. 요약(가중 평균순위 포함) + rows 반환. It is categorised as a Read tool in the Mimi Seed MCP Server, which means it retrieves data without modifying state.
Register the Mimi Seed MCP server in PolicyLayer and add a rule for gsc_search_analytics: 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 Mimi Seed. Nothing to install.
gsc_search_analytics is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the gsc_search_analytics 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 gsc_search_analytics. 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.
gsc_search_analytics is provided by the Mimi Seed MCP server (@yoonion/mimi-seed-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mimi Seed, and thousands of servers like it.
This server
Across the catalogue