sales_os_crew_check_in

SERVERMax MCP Server SOURCEdigital-crew-technologies/max-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/digital-crew-technologies-max-mcp-server/sales-os-crew-check-in.md

WHAT IT DOES

What sales_os_crew_check_in does on Max MCP Server

AI agents call sales_os_crew_check_in 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.

RISK

Why sales_os_crew_check_in is rated Low

Even though sales_os_crew_check_in 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

RECOMMENDED RULE

The rule that runs sales_os_crew_check_in 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 sales_os_crew_check_in, this is the rule to start with:

sales_os_crew_check_in Allowed

sales_os_crew_check_in is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sales_os_crew_check_in": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Max MCP Server, apply this rule, and every sales_os_crew_check_in call is checked against it from then on.

FAQ

Questions about sales_os_crew_check_in

What does the sales_os_crew_check_in tool do? +

Tell the team what this AI agent is doing so it shows as active in the Crew widget: call at the start of a work session and whenever the activity changes (state busy while working), and with state offline when done. Repeats within 10 s are coalesced (throttled: true); over 30 calls/min → 429 RATE_LIMITED. worker_id: 404 WORKER_NOT_FOUND, 409 WORKER_PAUSED. API-key connections only (a signed-in session gets 400). Scope workspace:write. Never retried. Returns {data: {recorded, member?}}. It is categorised as a Read tool in the Max MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on sales_os_crew_check_in? +

Register the Max MCP Server MCP server in PolicyLayer and add a rule for sales_os_crew_check_in: 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.

What risk level is sales_os_crew_check_in? +

sales_os_crew_check_in is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit sales_os_crew_check_in? +

Yes. Add a rate_limit block to the sales_os_crew_check_in 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.

How do I block sales_os_crew_check_in completely? +

Set action: deny in the PolicyLayer policy for sales_os_crew_check_in. 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.

What MCP server provides sales_os_crew_check_in? +

sales_os_crew_check_in 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.

KEEP EXPLORING

More on Max MCP Server, and thousands of servers like it.

This server

All 415 Max MCP Server tools →

Across the catalogue

get_product_sales on 08-AI-Business-Agent → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →