create_lead_source · Multilead Open API MCP Server MCP

WHAT IT DOES

What create_lead_source does on Multilead Open API MCP Server

AI agents use create_lead_source to create or update resources in Multilead Open API MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Multilead Open API MCP Server environment.

WHY IT NEEDS A POLICY

Why create_lead_source needs a policy

Creating a lead source is a reversible data modification operation—it establishes a new entity in the system but can be edited or deleted later. This fits the Write category rather than Execute (no code/script running) or Destructive (not irreversible). The tool description is empty, slightly reducing confidence, but the name combined with server context and sibling tools strongly suggests resource creation.

From the tool's definition Tool name 'create_lead_source' indicates creation of a new lead source resource. The server context shows this is a lead management platform (Multilead), and sibling tools include 'add_leads_to_campaign' and 'assign_tag_to_lead', confirming write operations…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_lead_source Rate-limited

create_lead_source 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": {
    "create_lead_source": {
      "limits": [
        {
          "counter": "create_lead_source_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Multilead Open API MCP Server, so you can run agents against it safely.

FAQ

Questions about create_lead_source

What does the create_lead_source tool do? +

create_lead_source. It is categorised as a Write tool in the Multilead Open API MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_lead_source? +

Register the Multilead Open API MCP Server MCP server in PolicyLayer and add a rule for create_lead_source: 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 Multilead Open API MCP Server. Nothing to install.

What risk level is create_lead_source? +

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

Can I rate-limit create_lead_source? +

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

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

create_lead_source is provided by the Multilead Open API MCP Server MCP server (vanman2024/multilead-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.