seo.url_metrics
Get detailed Ahrefs SEO metrics for a specific URL. Returns two sections: - page: backlinks, referring domains, estimated traffic, traffic value, organic keywords, URL rating, and word count on the page - domain: domain rating, rank, backlinks, referring domains, traffic, traffic value, and organ...
This record as markdown: /tools/io-github-vee3io-vee3/seo.url-metrics.md
What seo.url_metrics does on Vee3
AI agents call seo.url_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 |
|---|---|---|---|
url | string | Yes | Public page URL to analyze. |
Parameters from the server's own tool schema.
Why seo.url_metrics is rated Low
This tool retrieves and queries publicly available SEO metrics data from Ahrefs about a URL and domain. It performs no side effects, creates no resources, executes no code, and cannot delete or modify data. The blast radius of misuse is minimal—an agent could make excessive queries or map URLs of interest, but cannot harm systems or data.
From the tool's definition Tool name 'seo.url_metrics' and description explicitly state it 'Get detailed Ahrefs SEO metrics for a specific URL' and 'Returns' data sections without any modification, creation, deletion, or execution verbs.
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs seo.url_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.url_metrics, this is the rule to start with:
seo.url_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.url_metrics call is checked against it from then on.
Questions about seo.url_metrics
Get detailed Ahrefs SEO metrics for a specific URL. Returns two sections: - page: backlinks, referring domains, estimated traffic, traffic value, organic keywords, URL rating, and word count on the page - domain: domain rating, rank, backlinks, referring domains, traffic, traffic value, and organic keywords Cost = 10 tokens. It is categorised as a Read tool in the Vee3 MCP Server, which means it retrieves data without modifying state.
seo.url_metrics accepts 1 parameter: url. Required: url. 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.url_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.url_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.url_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.url_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.url_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