google-search-console.add_site

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

Medium RISK CLASS

Category Write

Parameters 11 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What google-search-console.add_site does on Vee3

AI agents use google-search-console.add_site to create or update resources in Vee3, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vee3 environment.

Parameter	Type	Required	Description
`site_url`	string	Yes	Domain or property to add. The user or agent passes a hostname (example.com), a domain property (sc-domain:example.com), or a URL (https://example.com/).

Parameters from the server's own tool schema.

RISK

Why google-search-console.add_site is rated Medium

Creates a new Search Console property and writes DNS records; reversible action.

From the tool's definition Add a domain as a Google Search Console property

Attacks that exploit this kind of access

RECOMMENDED RULE

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

google-search-console.add_site Rate-limited

google-search-console.add_site stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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.add_site": {
      "limits": [
        {
          "counter": "google-search-console.add_site_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT 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.add_site call is checked against it from then on.

FAQ

Questions about google-search-console.add_site

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

Add a domain as a Google Search Console property on Vee3's Search Console account. The user or agent can pass a domain, a domain property, or a URL. Vee3-managed domains are added and verified automatically. If the apex host uses URL forwarding, Vee3 writes a Google DNS CNAME record instead of a TXT record. If Google still needs time to verify, the response asks the agent to wait and retry this tool. If Vee3 cannot write DNS, the response includes dns_host_name, dns_record_type, and dns_token. Domains that are not managed by Vee3 return DNS TXT instructions so the user or agent can prove ownership, then retry this tool. After a site is added, call google-search-console.list_sites to see it, then use the other Search Console tools. Cost = 10 tokens. It is categorised as a Write tool in the Vee3 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

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

google-search-console.add_site accepts 1 parameter: site_url. Required: 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.add_site? +

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

google-search-console.add_site is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

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

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

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

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

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →