probe_server_runtime

SERVERSamarth Gtm Mcp SOURCEsamarth-gtm-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/probe-server-runtime.md

WHAT IT DOES

What probe_server_runtime does on Samarth Gtm Mcp

AI agents invoke probe_server_runtime to trigger actions in Samarth Gtm Mcp. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why probe_server_runtime is rated High

Triggers a live synthetic event into a production GA4 property, causing real external side effects.

From the tool's definition sends ONE labelled synthetic GA4 event... DELIVERS a hit into a production property

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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

probe_server_runtime Rate-limited

probe_server_runtime stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "probe_server_runtime": {
      "limits": [
        {
          "counter": "probe_server_runtime_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

FAQ

Questions about probe_server_runtime

What does the probe_server_runtime tool do? +

RUNTIME PROOF for a SERVER container: sends ONE labelled synthetic GA4 event (named samarth_probe_<id>, throwaway client id, debug_mode on) through the recorded tagging server and reads it back from the realtime report of the GA4 property. This is the only check that proves the round trip web -> tagging server -> GA4 relay -> property actually works; every other server check proves configuration only. It DELIVERS a hit into a production property, so it is human-approved and never runs on a schedule. Result status: pass (seen in realtime, with latency), not_verified (accepted by the server but not seen within the wait: realtime can lag, so this is NOT a failure), or send_failed (the server refused it: a 400 means no client claimed /g/collect). Pass measurementId when the server forwards more than one id. Takes up to 2 minutes. It is categorised as a Execute tool in the Samarth Gtm Mcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on probe_server_runtime? +

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

probe_server_runtime is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit probe_server_runtime? +

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

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

probe_server_runtime 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 254 Samarth Gtm tools → High-risk tools on this server →

Across the catalogue

propose_probe on 0sec → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →