audit_container

Inspect a GTM workspace for common analytics implementation issues.

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/audit-container.md

WHAT IT DOES

What audit_container does on Samarth Gtm Mcp

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

This tool retrieves and analyzes GTM container configuration to identify issues, performing no modifications, deletions, or external operations. It is a diagnostic/inspection function that returns findings without side effects. Confidence is high because the audit pattern, 'inspect' language, and server's read-only default posture all align clearly with the Read category.

From the tool's definition Tool name 'audit_container' with description 'Inspect a GTM workspace for common analytics implementation issues' — the verb 'inspect' and context of auditing indicates read-only query/analysis of existing GTM configuration.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

audit_container Allowed

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

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

FAQ

Questions about audit_container

What does the audit_container tool do? +

Inspect a GTM workspace for common analytics implementation issues. 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 audit_container? +

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

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

Can I rate-limit audit_container? +

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

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

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