list_workspace_roles
List custom roles with their object/field permissions and assignment counts. Returns {data: CustomRole[]}.
This record as markdown: /tools/digital-crew-technologies-max-mcp-server/list-workspace-roles.md
What list_workspace_roles does on Max MCP Server
AI agents call list_workspace_roles to retrieve information from Max MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_workspace_roles is rated Low
Tool retrieves role and permission information without modifying data or triggering external actions.
From the tool's definition List custom roles with their object/field permissions and assignment counts. Returns data.
Attacks that exploit this kind of access
The rule that runs list_workspace_roles safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Max MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_workspace_roles, this is the rule to start with:
list_workspace_roles 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 Max MCP Server, apply this rule, and every list_workspace_roles call is checked against it from then on.
Questions about list_workspace_roles
List custom roles with their object/field permissions and assignment counts. Returns {data: CustomRole[]}. It is categorised as a Read tool in the Max MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Max MCP Server MCP server in PolicyLayer and add a rule for list_workspace_roles: 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 Max MCP Server. Nothing to install.
list_workspace_roles 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 list_workspace_roles 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 list_workspace_roles. 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.
list_workspace_roles is provided by the Max MCP Server MCP server (digital-crew-technologies/max-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Max MCP Server, and thousands of servers like it.
This server
Across the catalogue