Pulse

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

7 write tools that can modify data. Rate limits recommended.

Last updated:

7 can modify or destroy data
22 read-only
29 tools total

7 Pulse 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 PULSE →

Free to start. No card required.

Read (22) Write / Execute (7) Destructive / Financial (0)
5,779 tokens of tool definitions, loaded on every request
2.9% of a 200k context window
486 heaviest tool: create_trip_skeleton

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

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

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "compare_destinations": {
    "limits": [
      {
        "counter": "compare_destinations_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 Pulse server in minutes. Tune the limits to your setup; PolicyLayer enforces it on every call.

ENFORCE ON MY PULSE →
How do I prevent bulk modifications through Pulse? +

The Pulse server has 7 write tools including convert_currency, create_trip_skeleton, generate_packing_list. 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 Pulse.

How many tools does the Pulse MCP server expose? +

29 tools across 2 categories: Read, Write. 22 are read-only. 7 can modify, create, or delete data.

How do I enforce a policy on Pulse? +

Register the Pulse 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.

Enforce policy on every Pulse tool call.

Deterministic rules across all 29 Pulse 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.