consent_banner_detect

Detect the consent banner (CMP) on a page without touching it. Identifies the vendor

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/consent-banner-detect.md

WHAT IT DOES

What consent_banner_detect does on Samarth Gtm Mcp

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

This tool performs a read-only detection and identification task. It observes the presence and vendor of a consent banner but does not modify, execute, delete, or trigger any actions. The explicit statement that it operates 'without touching' the banner confirms no side effects.

From the tool's definition Tool description states 'Detect the consent banner (CMP) on a page without touching it.' The phrase 'without touching it' explicitly indicates no modifications or side effects occur.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

consent_banner_detect Allowed

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

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

FAQ

Questions about consent_banner_detect

What does the consent_banner_detect tool do? +

Detect the consent banner (CMP) on a page without touching it. Identifies the vendor. 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 consent_banner_detect? +

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

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

Can I rate-limit consent_banner_detect? +

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

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

consent_banner_detect 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 →