create_salesforce_lead · OOSDK MCP Server MCP: Risk & Policy

WHAT IT DOES

What create_salesforce_lead does on OOSDK MCP Server

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

WHY IT NEEDS A POLICY

Why create_salesforce_lead needs a policy

This tool creates new lead records in Salesforce, which are reversible writes that modify the sales pipeline. While the empty description reduces confidence slightly, the name unambiguously indicates record creation. The severity is high because erroneous or malicious lead creation could pollute the sales database, trigger downstream automated workflows, and waste sales team resources on invalid prospects.

From the tool's definition Tool name 'create_salesforce_lead' indicates creation of a new Salesforce lead record. Description is empty, limiting evidence, but the verb 'create' and Salesforce context (a CRM system used for sales pipeline management) strongly suggest data creation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_salesforce_lead Rate-limited

create_salesforce_lead 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_salesforce_lead": {
      "limits": [
        {
          "counter": "create_salesforce_lead_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 OOSDK MCP Server, so you can run agents against it safely.

FAQ

Questions about create_salesforce_lead

What does the create_salesforce_lead tool do? +

create_salesforce_lead. It is categorised as a Write tool in the OOSDK 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_salesforce_lead? +

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

What risk level is create_salesforce_lead? +

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

Can I rate-limit create_salesforce_lead? +

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

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

create_salesforce_lead is provided by the OOSDK MCP Server MCP server (sunnylabtv-crypto/ai_mcp_multi_agent_oosdk-public). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.