get_workspace_profile
Fetch workspace profile settings (company info) for the authenticated workspace via DigitalCrew API. Uses the MCP connection Authorization: Bearer token when set.
This record as markdown: /tools/digital-crew-technologies-max-mcp-server/get-workspace-profile.md
What get_workspace_profile does on Max MCP Server
AI agents call get_workspace_profile 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 get_workspace_profile is rated Low
This tool exclusively retrieves workspace profile settings and company information for the authenticated workspace. It performs a read-only operation with no side effects, no data modification, no code execution, and no financial impact. The use of 'Fetch' and the absence of any write/delete/execute language confirms this is a Read category tool.
From the tool's definition Tool name 'get_workspace_profile' and description 'Fetch workspace profile settings (company info)' indicate data retrieval with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
The rule that runs get_workspace_profile 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 get_workspace_profile, this is the rule to start with:
get_workspace_profile 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 get_workspace_profile call is checked against it from then on.
Questions about get_workspace_profile
Fetch workspace profile settings (company info) for the authenticated workspace via DigitalCrew API. Uses the MCP connection Authorization: Bearer token when set. 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 get_workspace_profile: 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.
get_workspace_profile 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 get_workspace_profile 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 get_workspace_profile. 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.
get_workspace_profile 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