pulso_quien_soy

Confirma qué usuario y organización identifica el token (nombre, email, org).

SERVERPulso SOURCE@ruger/pulso-mcp

Low RISK CLASS

Category Other

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/ruger-pulso-mcp/pulso-quien-soy.md

WHAT IT DOES

What pulso_quien_soy does on Pulso

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

RISK

Why pulso_quien_soy is rated Low

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

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs pulso_quien_soy safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Pulso, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pulso_quien_soy, this is the rule to start with:

pulso_quien_soy Rate-limited

pulso_quien_soy gets a rate cap, and everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pulso_quien_soy": {
      "limits": [
        {
          "counter": "pulso_quien_soy_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

SET A RULE FOR THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Pulso, apply this rule, and every pulso_quien_soy call is checked against it from then on.

FAQ

Questions about pulso_quien_soy

What does the pulso_quien_soy tool do? +

Confirma qué usuario y organización identifica el token (nombre, email, org). It is categorised as a Other tool in the Pulso MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on pulso_quien_soy? +

Register the Pulso MCP server in PolicyLayer and add a rule for pulso_quien_soy: 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_quien_soy? +

pulso_quien_soy is a Other tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit pulso_quien_soy? +

Yes. Add a rate_limit block to the pulso_quien_soy 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_quien_soy completely? +

Set action: deny in the PolicyLayer policy for pulso_quien_soy. 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_quien_soy? +

pulso_quien_soy 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.

KEEP EXPLORING

More on Pulso, and thousands of servers like it.

This server

All 12 Pulso tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Tool risk categories →MCP tool →