google-search-console.get_site

Get one Search Console property for this account. Call google-search-console.list_sites to discover sites. Omit site_url to use the default property, or pass an exact site_url from that response, including unverified properties. Returns the property URL and permission level. Cost = 5 tokens.

SERVERVee3 SOURCEhttps://mcp.vee3.io/mcp

Low RISK CLASS

Category Read

Parameters 10 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-vee3io-vee3/google-search-console.get-site.md

WHAT IT DOES

What google-search-console.get_site does on Vee3

AI agents call google-search-console.get_site 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.

Parameter	Type	Required	Description
`site_url`	object	—	Optional property URL from google-search-console.list_sites. When omitted, the default property is used. The user or agent passes an exact site_url value from t

Parameters from the server's own tool schema.

RISK

Why google-search-console.get_site is rated Low

Retrieves metadata about a Search Console property; read-only operation with no side effects.

From the tool's definition Get one Search Console property, returns property URL and permission level.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs google-search-console.get_site 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.get_site, this is the rule to start with:

google-search-console.get_site Allowed

google-search-console.get_site 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": {
    "google-search-console.get_site": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect Vee3, apply this rule, and every google-search-console.get_site call is checked against it from then on.

FAQ

Questions about google-search-console.get_site

What does the google-search-console.get_site tool do? +

What parameters does google-search-console.get_site accept? +

google-search-console.get_site accepts 1 parameter: site_url. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on google-search-console.get_site? +

Register the Vee3 MCP server in PolicyLayer and add a rule for google-search-console.get_site: 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.

What risk level is google-search-console.get_site? +

google-search-console.get_site is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit google-search-console.get_site? +

Yes. Add a rate_limit block to the google-search-console.get_site 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 google-search-console.get_site completely? +

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

google-search-console.get_site 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.

KEEP EXPLORING

More on Vee3, and thousands of servers like it.

This server

All 269 Vee3 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 →