verify_server_endpoint

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/verify-server-endpoint.md

WHAT IT DOES

What verify_server_endpoint does on Samarth Gtm Mcp

AI agents call verify_server_endpoint 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 verify_server_endpoint is rated Low

Performs a read-only HTTP GET health check with no side effects.

From the tool's definition GET <serverUrl>/healthy to confirm host is deployed and reachable

Attacks that exploit this kind of access

RECOMMENDED RULE

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

verify_server_endpoint Allowed

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

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

FAQ

Questions about verify_server_endpoint

What does the verify_server_endpoint tool do? +

Runtime check for a server-side GTM tagging server: GET <serverUrl>/healthy to confirm the host is deployed and reachable. https-only, public hosts only. Use after deploying a tagging server, or when an audit flags a missing tagging server URL. 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 verify_server_endpoint? +

Register the Samarth Gtm MCP server in PolicyLayer and add a rule for verify_server_endpoint: 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 verify_server_endpoint? +

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

Can I rate-limit verify_server_endpoint? +

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

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

verify_server_endpoint 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

The MCP Attack Database →

Guides

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