googleTagManager_create_user_permission

Grant a user access to a GTM account

SERVERScopeGate SOURCEhttps://mcp.scopegate.cloud/{api_key}
Medium RISK CLASS
Category Write
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-alifanov-scopegate/googletagmanager-create-user-permission.md

What googleTagManager_create_user_permission does on ScopeGate

AI agents use googleTagManager_create_user_permission to create or update resources in ScopeGate, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ScopeGate environment.

Why googleTagManager_create_user_permission is rated Medium

Granting user permissions is a Write operation—it creates or modifies access control entries. While it could have significant downstream effects if misused (granting overly broad access), it is reversible (permissions can be revoked), so it does not qualify as Destructive.

From the tool's definition Tool name indicates 'create_user_permission' which modifies access control by granting a user to a GTM account. This is a reversible modification of permissions/access state.

Questions about googleTagManager_create_user_permission

What does the googleTagManager_create_user_permission tool do? +

Grant a user access to a GTM account. It is categorised as a Write tool in the ScopeGate MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on googleTagManager_create_user_permission? +

Register the ScopeGate MCP server in PolicyLayer and add a rule for googleTagManager_create_user_permission: 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 ScopeGate. Nothing to install.

What risk level is googleTagManager_create_user_permission? +

googleTagManager_create_user_permission is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit googleTagManager_create_user_permission? +

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

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

googleTagManager_create_user_permission is provided by the ScopeGate MCP server (https://mcp.scopegate.cloud/{api_key}). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on ScopeGate, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of ScopeGate's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.