onloon-crm-contact__scheduleFollowup

创建跟进日程。

SERVERLxwl SOURCE@lxwl/mcp-server

Medium RISK CLASS

Category Write

Parameters 40 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/lxwl-mcp-server/onloon-crm-contact--schedulefollowup.md

WHAT IT DOES

What onloon-crm-contact__scheduleFollowup does on Lxwl

AI agents use onloon-crm-contact__scheduleFollowup to create or update resources in Lxwl, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Lxwl environment.

Parameter	Type	Required
`dueAt`	string	—
`title`	string	—
`confirmed`	boolean	—
`contactId`	string	—

Parameters from the server's own tool schema.

RISK

Why onloon-crm-contact__scheduleFollowup is rated Medium

An AI agent can call onloon-crm-contact__scheduleFollowup faster than any human can review: one bad instruction and it creates or modifies resources in Lxwl by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs onloon-crm-contact__scheduleFollowup safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Lxwl, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For onloon-crm-contact__scheduleFollowup, this is the rule to start with:

onloon-crm-contact__scheduleFollowup Rate-limited

onloon-crm-contact__scheduleFollowup stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "onloon-crm-contact__scheduleFollowup": {
      "limits": [
        {
          "counter": "onloon-crm-contact__schedulefollowup_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Lxwl, apply this rule, and every onloon-crm-contact__scheduleFollowup call is checked against it from then on.

FAQ

Questions about onloon-crm-contact__scheduleFollowup

What does the onloon-crm-contact__scheduleFollowup tool do? +

创建跟进日程。. It is categorised as a Write tool in the Lxwl MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does onloon-crm-contact__scheduleFollowup accept? +

onloon-crm-contact__scheduleFollowup accepts 4 parameters: dueAt, title, confirmed, contactId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on onloon-crm-contact__scheduleFollowup? +

Register the Lxwl MCP server in PolicyLayer and add a rule for onloon-crm-contact__scheduleFollowup: 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 Lxwl. Nothing to install.

What risk level is onloon-crm-contact__scheduleFollowup? +

onloon-crm-contact__scheduleFollowup is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit onloon-crm-contact__scheduleFollowup? +

Yes. Add a rate_limit block to the onloon-crm-contact__scheduleFollowup 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 onloon-crm-contact__scheduleFollowup completely? +

Set action: deny in the PolicyLayer policy for onloon-crm-contact__scheduleFollowup. 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 onloon-crm-contact__scheduleFollowup? +

onloon-crm-contact__scheduleFollowup is provided by the Lxwl MCP server (@lxwl/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 Lxwl, and thousands of servers like it.

This server

All 236 Lxwl tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →