asignar_entrada
Archiva una entrada del inbox bajo uno o más clientes: es la segunda criba, la decisión de que esa oportunidad es relevante para ese cliente. Indica 'entrada_id' (el 'id' de listar_entradas) y 'clientes' (nombre o nombres separados por comas, tal como aparecen en listar_clientes). La entrada pasa...
This record as markdown: /tools/es-boletinclaro-mcp/asignar-entrada.md
What asignar_entrada does on Boletín Claro
AI agents call asignar_entrada as a supporting operation in Boletín Claro workflows.
| Parameter | Type | Required | Description |
|---|---|---|---|
clientes | string | Yes | Cliente o clientes bajo los que archivar la entrada, por su nombre y separados por comas (tal como aparecen en listar_clientes). Ej: 'Acme S.L.' o 'Acme S.L., B |
entrada_id | string | Yes | Id de la entrada a archivar, tal como aparece en listar_entradas (campo 'id'). |
Parameters from the server's own tool schema.
Why asignar_entrada is rated Low
Without any rule in front of it, every call an agent makes to asignar_entrada happens silently: no trail, no cap, no way to know it misbehaved until something breaks downstream.
Attacks that exploit this kind of access
The rule that runs asignar_entrada 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 asignar_entrada, this is the rule to start with:
asignar_entrada gets a rate cap, and 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 asignar_entrada call is checked against it from then on.
Questions about asignar_entrada
Archiva una entrada del inbox bajo uno o más clientes: es la segunda criba, la decisión de que esa oportunidad es relevante para ese cliente. Indica 'entrada_id' (el 'id' de listar_entradas) y 'clientes' (nombre o nombres separados por comas, tal como aparecen en listar_clientes). La entrada pasa al flujo de trabajo de cada cliente y la alerta que la detectó se vincula automáticamente al cliente. Requiere tener el modo clientes activado. Coste: 0 créditos de lectura; se mantienen los límites y confirmaciones del plan. It is categorised as a Other tool in the Boletín Claro MCP Server, which means it performs auxiliary operations.
asignar_entrada accepts 2 parameters: clientes, entrada_id. Required: clientes, entrada_id. 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 asignar_entrada: 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.
asignar_entrada is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the asignar_entrada 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 asignar_entrada. 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.
asignar_entrada 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