pages.get

Get details for one static website this Vee3 account hosts. Returns name, status, public URL, preview hostname on vee3.site, attached custom domain if any, and timestamps. Cost = 5 tokens.

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

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-vee3io-vee3/pages.get.md

WHAT IT DOES

What pages.get does on Vee3

AI agents call pages.get 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
`page_id`	string	Yes	Page id to look up.

Parameters from the server's own tool schema.

RISK

Why pages.get is rated Low

Retrieves website metadata without modifying or deleting data.

From the tool's definition Get details for one static website this Vee3 account hosts.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs pages.get 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 pages.get, this is the rule to start with:

pages.get Allowed

pages.get 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": {
    "pages.get": {}
  }
}

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

FAQ

Questions about pages.get

What does the pages.get tool do? +

Get details for one static website this Vee3 account hosts. Returns name, status, public URL, preview hostname on vee3.site, attached custom domain if any, and timestamps. Cost = 5 tokens. It is categorised as a Read tool in the Vee3 MCP Server, which means it retrieves data without modifying state.

What parameters does pages.get accept? +

pages.get accepts 1 parameter: page_id. Required: page_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on pages.get? +

Register the Vee3 MCP server in PolicyLayer and add a rule for pages.get: 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 pages.get? +

pages.get is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit pages.get? +

Yes. Add a rate_limit block to the pages.get 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 pages.get completely? +

Set action: deny in the PolicyLayer policy for pages.get. 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 pages.get? +

pages.get 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

Roll out MCP under one policy →Data exfiltration →MCP token cost →