enrich_organization
Run Claire deep-research on an organization and save the result onto the record. SYNCHRONOUS — waits for Claire (may take 30-180s) and returns {status} (
This record as markdown: /tools/digital-crew-technologies-max-mcp-server/enrich-organization.md
What enrich_organization does on Max MCP Server
AI agents invoke enrich_organization to trigger actions in Max MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why enrich_organization is rated High
This tool triggers an external AI deep-research process (Claire) that runs for up to 3 minutes, then writes/saves results to a record. It initiates an external operation with non-trivial side effects (saving enriched data to the record). The 'execute and save' pattern — running an external process and persisting its output — places this in Execute territory, with Write as a secondary effect.
From the tool's definition 'Run Claire deep-research on an organization and save the result onto the record. SYNCHRONOUS — waits for Claire (may take 30-180s)'
Attacks that exploit this kind of access
The rule that runs enrich_organization 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 enrich_organization, this is the rule to start with:
enrich_organization stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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 enrich_organization call is checked against it from then on.
Questions about enrich_organization
Run Claire deep-research on an organization and save the result onto the record. SYNCHRONOUS — waits for Claire (may take 30-180s) and returns {status} (. It is categorised as a Execute tool in the Max MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Max MCP Server MCP server in PolicyLayer and add a rule for enrich_organization: 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.
enrich_organization is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the enrich_organization 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 enrich_organization. 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.
enrich_organization 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.
Across the catalogue