New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

Pulso

12 tools. 12 can modify or destroy data without limits.

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

Last updated:

12 can modify or destroy data
0 read-only
12 tools total

Community server · catalogue entry checked 17/09/2026 · full schemas captured for 8 of 12 tools

How to control Pulso ↓

What Pulso exposes to your agents

Read (0) Write / Execute (0) Destructive / Financial (1)

What Pulso costs in tokens

978 tokens of tool definitions, loaded on every request
0.5% of a 200k context window
232 heaviest tool: pulso_cargar_hora
Critical Risk

The most dangerous Pulso tools

12 of Pulso's 12 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

How to control Pulso

PolicyLayer is an MCP gateway — it sits between your AI agents and Pulso, and nothing reaches the server without passing your rules. These are the rules we recommend:

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

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

  1. Create a free account and register Pulso — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON PULSO →

Instant setup, no code required.

All 12 Pulso tools

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

Questions about Pulso

Can an AI agent delete data through the Pulso MCP server? +

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

How many tools does the Pulso MCP server expose? +

12 tools across 2 categories: Destructive, Other. 0 are read-only. 12 can modify, create, or delete data.

How do I enforce a policy on Pulso? +

Register the Pulso 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 Pulso tool call.

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

Instant setup, no code required.

12 Pulso tools catalogued and risk-classified — across an index of 46,500+ MCP servers.

// WHERE THIS COMES FROM

These policies come from Pulso's registry record.

The record behind this page: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.