detect_page_phone_numbers

Scan one or more live page URLs and return every UNIQUE phone number on them, merged across pages and normalized to E.164 where possible. Read-only.

SERVERSamarth Gtm Mcp SOURCEsamarth-gtm-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/detect-page-phone-numbers.md

WHAT IT DOES

What detect_page_phone_numbers does on Samarth Gtm Mcp

AI agents call detect_page_phone_numbers to retrieve information from Samarth Gtm Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why detect_page_phone_numbers is rated Low

Retrieves publicly visible phone numbers from web pages without modification or side effects.

From the tool's definition Scan live page URLs and return phone numbers. Read-only.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs detect_page_phone_numbers safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Samarth Gtm Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For detect_page_phone_numbers, this is the rule to start with:

detect_page_phone_numbers Allowed

detect_page_phone_numbers 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": {
    "detect_page_phone_numbers": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect Samarth Gtm Mcp, apply this rule, and every detect_page_phone_numbers call is checked against it from then on.

FAQ

Questions about detect_page_phone_numbers

What does the detect_page_phone_numbers tool do? +

Scan one or more live page URLs and return every UNIQUE phone number on them, merged across pages and normalized to E.164 where possible. Read-only. It is categorised as a Read tool in the Samarth Gtm Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on detect_page_phone_numbers? +

Register the Samarth Gtm MCP server in PolicyLayer and add a rule for detect_page_phone_numbers: 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 Samarth Gtm Mcp. Nothing to install.

What risk level is detect_page_phone_numbers? +

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

Can I rate-limit detect_page_phone_numbers? +

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

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

detect_page_phone_numbers is provided by the Samarth Gtm MCP server (samarth-gtm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Samarth Gtm, and thousands of servers like it.

This server

All 236 Samarth Gtm tools →

Across the catalogue

detect_slop on Slop Cop → The MCP Attack Database →

Guides

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