dials_listMessagingBrands
List scoped messaging brand configuration (GET /v1/dials/messaging/brands) [service status: unverified]
This record as markdown: /tools/lifesi-genesis-mcp/dials-listmessagingbrands.md
What dials_listMessagingBrands does on Genesis
AI agents call dials_listMessagingBrands to retrieve information from Genesis without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
projectId | string | Yes | Selected Dials scope. |
platformId | string | — | Selected data platform. Omitted defaults to dials in the backend; selection does not grant organization authority. |
workspaceId | string | Yes | Selected Dials scope. |
environmentId | string | Yes | Selected Dials scope. |
organizationId | string | Yes | Must match the authenticated organization. |
Parameters from the server's own tool schema.
Why dials_listMessagingBrands is rated Low
Even though dials_listMessagingBrands only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs dials_listMessagingBrands safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Genesis, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For dials_listMessagingBrands, this is the rule to start with:
dials_listMessagingBrands is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Genesis, apply this rule, and every dials_listMessagingBrands call is checked against it from then on.
Questions about dials_listMessagingBrands
List scoped messaging brand configuration (GET /v1/dials/messaging/brands) [service status: unverified]. It is categorised as a Read tool in the Genesis MCP Server, which means it retrieves data without modifying state.
dials_listMessagingBrands accepts 5 parameters: projectId, platformId, workspaceId, environmentId, organizationId. Required: projectId, workspaceId, environmentId, organizationId. The full parameter table on this page comes from the server's own tool schema.
Register the Genesis MCP server in PolicyLayer and add a rule for dials_listMessagingBrands: 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 Genesis. Nothing to install.
dials_listMessagingBrands is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the dials_listMessagingBrands 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.
Set action: deny in the PolicyLayer policy for dials_listMessagingBrands. 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.
dials_listMessagingBrands is provided by the Genesis MCP server (@lifesi/genesis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Genesis, and thousands of servers like it.
This server
Across the catalogue