get_top_performing_content
AI agents call get_top_performing_content to retrieve information from Google Search Console MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves performance metrics and content data from Search Console for analysis and reporting. No evidence of modification, deletion, code execution, or financial operations. The minimal confidence deduction (0.85 vs 1.0) reflects the empty tool description, though contextual evidence from sibling tools and server purpose is clear.
From the tool's definition Tool name 'get_top_performing_content' and server purpose indicate data retrieval from Google Search Console. Sibling tools (compare_time_periods, get_search_trends, list_sites, query_search_analytics) are all analytics queries without side effects.
Documented attack patterns abuse exactly the kind of access get_top_performing_content gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Google Search Console MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_top_performing_content:
{
"version": "1",
"default": "deny",
"tools": {
"get_top_performing_content": {}
}
}get_top_performing_content is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_top_performing_content. It is categorised as a Read tool in the Google Search Console MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Google Search Console MCP Server MCP server in PolicyLayer and add a rule for get_top_performing_content: 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 Google Search Console MCP Server. Nothing to install.
get_top_performing_content 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 get_top_performing_content 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 get_top_performing_content. 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.
get_top_performing_content is provided by the Google Search Console MCP Server MCP server (seotesting-com/gsc-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Google Search Console MCP Server, 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.
5 Google Search Console MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.