Skip to main content
Glama
google

Chrome Enterprise Premium MCP Server

Official
by google

create_chrome_dlp_rule

Creates a Chrome DLP rule to protect browser actions (uploads, downloads, printing) per organizational unit.

Instructions

Creates a new Chrome DLP rule for a specific Organizational Unit. Applies browser-level protection (uploads, downloads, printing). For safety reasons, this MCP tool is disabled from creating 'ACTIVE' rules with a 'BLOCK' action. You can create 'INACTIVE' 'BLOCK' rules and enable them later in the UI, or create 'ACTIVE' 'WARN' or 'AUDIT' rules.

To ensure technical accuracy and verify trigger compatibility, you should retrieve the full technical reference using 'get_document' for '11-dlp-rule-reference' before using this tool.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stateNoRule state (defaults to ACTIVE): - ACTIVE: The rule is currently enforced. - INACTIVE: The rule is saved but not currently enforced.
actionYesAction to take when the rule is triggered. AUDIT mode is silent and logs events without notifying or blocking the user.
triggersYesList of Chrome triggers: - FILE_UPLOAD: Scanning files that are uploaded. - FILE_DOWNLOAD: Scanning files that are downloaded. - WEB_CONTENT_UPLOAD: Scanning text that is copy-pasted. - PRINT: Scanning pages that are printed. - URL_NAVIGATION: Scanning URLs when visited.
conditionNoCEL condition string. To ensure technical accuracy and verify trigger compatibility, you should retrieve the full technical reference using 'get_document' for '11-dlp-rule-reference' before formulating a condition.
orgUnitIdYesThe target Organizational Unit ID
customerIdNoThe Chrome customer ID (e.g. C012345).
dataMaskingNoData masking configurations (supports custom regular expressions and data masking detectors). The 'dataMasking' parameter is only supported with the 'URL_NAVIGATION' trigger and 'WARN' or 'AUDIT' actions. Currently, only custom regular expressions and data masking detectors are supported for data masking (word lists and URL lists are not supported).
descriptionNoDescription of the rule.
displayNameYesThe display name of the rule. Will be automatically prefixed with '🤖 '.
saveContentNoWhether to save the content that triggered the rule.
customMessageNoCustom message to display to the user. The 'customMessage' parameter is supported with 'BLOCK' and 'WARN' actions, and must be 300 characters or less. Only <a> tags with href attributes are allowed.
blockScreenshotNoWhether to block screenshots when the rule is triggered. The 'blockScreenshot' parameter (which also restricts screen-sharing) is only supported with the 'URL_NAVIGATION' trigger and 'WARN' or 'AUDIT' actions.
watermarkMessageNoWatermark message to display when the rule is triggered. The 'watermarkMessage' parameter is only supported with the 'URL_NAVIGATION' trigger and 'WARN' or 'AUDIT' actions, and must be 60 characters or less.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dlpRuleYes
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description fully carries the burden. Discloses critical behavioral constraints: forbidden combos, display name prefix, trigger-specific parameter support, and need for reference document. Exceeds expectations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool description is 3 concise sentences, front-loaded with purpose and usage constraints. Parameter descriptions in schema are verbose but necessary for documenting constraints. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers safety, constraints, prerequisites. Output schema exists (though not shown) so return info not needed. Could mention idempotency or error handling, but overall complete for a creation tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but description adds significant value: cross-parameter compatibility (e.g., dataMasking only with URL_NAVIGATION and WARN/AUDIT), blockScreenshot constraints, customMessage limitations. These are not in the schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states it creates a Chrome DLP rule for an OU. Verb 'creates' and resource 'Chrome DLP rule' are specific. Distinguishes from sibling tools like get_dlp_rule or list_dlp_rules, but could explicitly differentiate from create_default_dlp_rules.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit safety restrictions (no ACTIVE+BLOCK) and alternatives ('use INACTIVE BLOCK or ACTIVE WARN/AUDIT'). Advises to consult get_document for technical reference. Lacks direct comparison to other create tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/google/chrome-enterprise-premium-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server