consent_compliance_audit

What consent_compliance_audit does on Samarth Gtm Mcp

AI agents invoke consent_compliance_audit 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.

Why consent_compliance_audit is rated High

The tool runs an 'audit agent' that performs active crawling and form inventory actions on specified websites. This goes beyond read-only data retrieval; it executes a complex, autonomous process that crawls pages and performs analysis. While labeled as an 'audit' function, the active crawling behavior constitutes code/agent execution against external systems.

From the tool's definition Tool description states 'Run the full audit agent against a website: crawls same-site pages, inventories forms' — this actively executes a crawling operation and systematic audit process against external websites, triggering external operations whose effects…

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

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

Questions about consent_compliance_audit