seo.keyword_metrics
Get SEO metrics for a search keyword in a specific country market. Returns keyword, searchVolume, clicks, cpc, difficulty, globalSearchVolume, and trafficPotential. Cost = 10 tokens.
This record as markdown: /tools/io-github-vee3io-vee3/seo.keyword-metrics.md
What seo.keyword_metrics does on Vee3
AI agents call seo.keyword_metrics 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 |
|---|---|---|---|
country | string | — | 2-letter ISO country code for the target market (default us). Use seo.country_codes for supported values. |
keyword | string | Yes | Search keyword or phrase to analyze. |
Parameters from the server's own tool schema.
Why seo.keyword_metrics is rated Low
This tool queries and retrieves SEO analytics data for a keyword in a specified market. It has no side effects, does not modify any data, execute code, or trigger external operations. The returned metrics are informational only. It is clearly a Read operation with low severity since misuse would only expose market analytics data without enabling harmful actions.
From the tool's definition Tool description states it 'Get[s] SEO metrics' and returns data fields (keyword, searchVolume, clicks, cpc, difficulty, globalSearchVolume, trafficPotential).
Attacks that exploit this kind of access
The rule that runs seo.keyword_metrics 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 seo.keyword_metrics, this is the rule to start with:
seo.keyword_metrics 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 seo.keyword_metrics call is checked against it from then on.
Questions about seo.keyword_metrics
Get SEO metrics for a search keyword in a specific country market. Returns keyword, searchVolume, clicks, cpc, difficulty, globalSearchVolume, and trafficPotential. Cost = 10 tokens. It is categorised as a Read tool in the Vee3 MCP Server, which means it retrieves data without modifying state.
seo.keyword_metrics accepts 2 parameters: country, keyword. Required: keyword. The full parameter table on this page comes from the server's own tool schema.
Register the Vee3 MCP server in PolicyLayer and add a rule for seo.keyword_metrics: 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.
seo.keyword_metrics 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 seo.keyword_metrics 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 seo.keyword_metrics. 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.
seo.keyword_metrics 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