# pulso_resumen

Horas por proyecto en un rango (semana, mes o últimos 30 días).

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

## Facts

- Tool: `pulso_resumen`
- 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: Other (Low risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 1
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `rango` | string | no | default: semana |

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_resumen",
    "arguments": {}
  }
}
```

## Why pulso_resumen is rated Low

Without any rule in front of it, every call an agent makes to pulso_resumen happens silently: no trail, no cap, no way to know it misbehaved until something breaks downstream.

## Use case

AI agents call pulso_resumen as a supporting operation in Pulso workflows.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "pulso_resumen": {
      "limits": [
        {
          "counter": "pulso_resumen_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Pulso (11)

- `pulso_borrar_hora` — Destructive — https://policylayer.com/tools/ruger-pulso-mcp/pulso-borrar-hora.md
- `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_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