google-search-console.list_sites
List Search Console properties for this account. Returns Vee3-managed domains plus sites added with google-search-console.add_site. Call this to discover sites, then omit site_url on later calls to use the default property, or pass an exact site_url from this response. If no properties appear, ad...
This record as markdown: /tools/io-github-vee3io-vee3/google-search-console.list-sites.md
What google-search-console.list_sites does on Vee3
AI agents call google-search-console.list_sites to retrieve information from Vee3 without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why google-search-console.list_sites is rated Low
Tool retrieves account properties and metadata without modifying data or triggering external side effects.
From the tool's definition List Search Console properties for this account. Returns Vee3-managed domains plus sites added.
Attacks that exploit this kind of access
The rule that runs google-search-console.list_sites safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Vee3, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For google-search-console.list_sites, this is the rule to start with:
google-search-console.list_sites 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 Vee3, apply this rule, and every google-search-console.list_sites call is checked against it from then on.
Questions about google-search-console.list_sites
List Search Console properties for this account. Returns Vee3-managed domains plus sites added with google-search-console.add_site. Call this to discover sites, then omit site_url on later calls to use the default property, or pass an exact site_url from this response. If no properties appear, add a site with google-search-console.add_site or register a domain with domains.register. Cost = 5 tokens. It is categorised as a Read tool in the Vee3 MCP Server, which means it retrieves data without modifying state.
Register the Vee3 MCP server in PolicyLayer and add a rule for google-search-console.list_sites: 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 Vee3. Nothing to install.
google-search-console.list_sites 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 google-search-console.list_sites 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 google-search-console.list_sites. 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.
google-search-console.list_sites is provided by the Vee3 MCP server (https://mcp.vee3.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Vee3, and thousands of servers like it.
This server
Across the catalogue