JustCall

29 tools. 8 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated:

8 can modify or destroy data
21 read-only
29 tools total

8 JustCall tools can modify or destroy data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE JUSTCALL →

Free to start. No card required.

Read (21) Write / Execute (7) Destructive / Financial (1)
3,578 tokens of tool definitions, loaded on every request
1.8% of a 200k context window
695 heaviest tool: list_calls

Destructive tools (delete_sms_tag) permanently delete resources. There is no undo. An agent calling these in a retry loop causes irreversible damage.

Write operations (create_campaign, create_contact, create_sms_tag) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.

Deny destructive operations
{
  "delete_sms_tag": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations
{
  "create_campaign": {
    "limits": [
      {
        "counter": "create_campaign_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "check_sms_reply": {
    "limits": [
      {
        "counter": "check_sms_reply_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Get this policy live on your own JustCall server in minutes. Tune the limits to your setup; PolicyLayer enforces it on every call.

ENFORCE ON MY JUSTCALL →
Can an AI agent delete data through the JustCall MCP server? +

Yes. The JustCall server exposes 1 destructive tools including delete_sms_tag. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through JustCall? +

The JustCall server has 7 write tools including create_campaign, create_contact, create_sms_tag. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach JustCall.

How many tools does the JustCall MCP server expose? +

29 tools across 3 categories: Destructive, Read, Write. 21 are read-only. 8 can modify, create, or delete data.

How do I enforce a policy on JustCall? +

Register the JustCall MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Other MCP servers with similar tools.

Starter policies for each. Same risk classification, live on your fleet in minutes.

Enforce policy on every JustCall tool call.

Deterministic rules across all 29 JustCall tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.