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

pulso_borrar_hora

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

SERVERPulso SOURCE@ruger/pulso-mcp
Critical RISK CLASS
Category Destructive
Parameters 11 required
Recommended Hiddensee the rule below
Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/ruger-pulso-mcp/pulso-borrar-hora.md

What pulso_borrar_hora does on Pulso

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.

ParameterTypeRequiredDescription
id string Yes id de la entrada a borrar

Parameters from the server's own tool schema.

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.

Questions about pulso_borrar_hora

What does the pulso_borrar_hora tool do? +

Borra (soft-delete) una hora tuya por id. Se puede restaurar desde Pulso. It is categorised as a Destructive tool in the Pulso MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

What parameters does pulso_borrar_hora accept? +

pulso_borrar_hora accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on pulso_borrar_hora? +

Register the Pulso MCP server in PolicyLayer and add a rule for pulso_borrar_hora: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Pulso. Nothing to install.

What risk level is pulso_borrar_hora? +

pulso_borrar_hora is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit pulso_borrar_hora? +

Yes. Add a rate_limit block to the pulso_borrar_hora rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block pulso_borrar_hora completely? +

Set action: deny in the PolicyLayer policy for pulso_borrar_hora. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides pulso_borrar_hora? +

pulso_borrar_hora is provided by the Pulso MCP server (@ruger/pulso-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Pulso, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Pulso's. Pull the full record:

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.