listar_entradas
Devuelve el inbox: las entradas que han encajado con tus alertas pero que aún no has archivado bajo ningún cliente. Es la primera criba de Boletín Claro; revísalas para decidir, con el contexto de cada cliente (listar_clientes), cuáles son relevantes y para quién. Cada entrada trae su 'id' para a...
This record as markdown: /tools/es-boletinclaro-mcp/listar-entradas.md
What listar_entradas does on Boletín Claro
AI agents call listar_entradas to retrieve information from Boletín Claro without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
alerta | string | — | Opcional. Acota el inbox a las entradas de una alerta concreta, por su nombre (tal como aparece en listar_clientes o listar_mis_alertas). |
limite | integer | — | Número máximo de entradas a devolver (por defecto 25, máximo 60). |
Parameters from the server's own tool schema.
Why listar_entradas is rated Low
This tool retrieves and lists inbox entries matching alerts. It only reads/queries data with no side effects, creation, modification, or deletion of any data.
From the tool's definition Devuelve el inbox: las entradas que han encajado con tus alertas pero que aún no has archivado
Attacks that exploit this kind of access
The rule that runs listar_entradas safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Boletín Claro, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For listar_entradas, this is the rule to start with:
listar_entradas is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Boletín Claro, apply this rule, and every listar_entradas call is checked against it from then on.
Questions about listar_entradas
Devuelve el inbox: las entradas que han encajado con tus alertas pero que aún no has archivado bajo ningún cliente. Es la primera criba de Boletín Claro; revísalas para decidir, con el contexto de cada cliente (listar_clientes), cuáles son relevantes y para quién. Cada entrada trae su 'id' para asignarla con asignar_entrada. Parámetros opcionales: 'limite' (por defecto 25, máximo 60) y 'alerta' (acota a una alerta por su nombre). Requiere tener el modo clientes activado. It is categorised as a Read tool in the Boletín Claro MCP Server, which means it retrieves data without modifying state.
listar_entradas accepts 2 parameters: alerta, limite. The full parameter table on this page comes from the server's own tool schema.
Register the Boletín Claro MCP server in PolicyLayer and add a rule for listar_entradas: 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 Boletín Claro. Nothing to install.
listar_entradas is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the listar_entradas 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.
Set action: deny in the PolicyLayer policy for listar_entradas. 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.
listar_entradas is provided by the Boletín Claro MCP server (https://boletinclaro.es/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Boletín Claro, and thousands of servers like it.
This server
Across the catalogue