# pulso_borrar_hora

Borra (soft-delete) una hora tuya por id. Se puede restaurar desde Pulso.

Agent View of the PolicyLayer registry record for `pulso_borrar_hora`. HTML page: https://policylayer.com/tools/ruger-pulso-mcp/pulso-borrar-hora

## Facts

- Tool: `pulso_borrar_hora`
- Server: Pulso (`@ruger/pulso-mcp`) — https://policylayer.com/tools/ruger-pulso-mcp.md
- Install: `npx -y @ruger/pulso-mcp`
- Homepage: https://www.npmjs.com/package/@ruger/pulso-mcp
- Risk category: Destructive (Critical risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 1 (1 required)
- Recommended policy verdict: Hidden

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `id` | string | yes | id de la entrada a borrar |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "pulso_borrar_hora",
    "arguments": {
      "id": "<id>"
    }
  }
}
```

## Why pulso_borrar_hora is rated Critical

An AI agent that decides to call pulso_borrar_hora doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Pulso is gone. There is no undo for destructive operations.

## Use case

AI agents call pulso_borrar_hora to permanently remove resources in Pulso, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

## Recommended policy (PolicyLayer)

Verdict: **Hidden**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Pulso:

```json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "pulso_borrar_hora"
  ]
}
```

## Other tools on Pulso (11)

- `pulso_arrancar_timer` — Other — https://policylayer.com/tools/ruger-pulso-mcp/pulso-arrancar-timer.md
- `pulso_cargar_hora` — Other — https://policylayer.com/tools/ruger-pulso-mcp/pulso-cargar-hora.md
- `pulso_editar_hora` — Other — https://policylayer.com/tools/ruger-pulso-mcp/pulso-editar-hora.md
- `pulso_hoy` — Other — https://policylayer.com/tools/ruger-pulso-mcp/pulso-hoy.md
- `pulso_listar_horas` — Other — https://policylayer.com/tools/ruger-pulso-mcp/pulso-listar-horas.md
- `pulso_parar_timer` — Other — https://policylayer.com/tools/ruger-pulso-mcp/pulso-parar-timer.md
- `pulso_proyectos` — Other — https://policylayer.com/tools/ruger-pulso-mcp/pulso-proyectos.md
- `pulso_quien_soy` — Other — https://policylayer.com/tools/ruger-pulso-mcp/pulso-quien-soy.md
- `pulso_registrar` — Other — https://policylayer.com/tools/ruger-pulso-mcp/pulso-registrar.md
- `pulso_resumen` — Other — https://policylayer.com/tools/ruger-pulso-mcp/pulso-resumen.md
- `pulso_timer` — Other — https://policylayer.com/tools/ruger-pulso-mcp/pulso-timer.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=ruger-pulso-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/ruger-pulso-mcp