# listar_tickets_post

A read tool on the MCP Officegest MCP server.

Agent View of the PolicyLayer registry record for `listar_tickets_post`. HTML page: https://policylayer.com/tools/rubencodex86-officegest-api-v2-mcp/listar-tickets-post

## Facts

- Tool: `listar_tickets_post`
- Server: MCP Officegest (`rubencodex86/officegest-api-v2-mcp`) — https://policylayer.com/tools/rubencodex86-officegest-api-v2-mcp.md
- Homepage: https://github.com/rubencodex86/officegest-api-v2-mcp
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "listar_tickets_post",
    "arguments": {}
  }
}
```

## Why listar_tickets_post is rated Low

'Listar' in Portuguese means 'to list', suggesting a read/query operation to retrieve tickets. However, the use of POST (rather than GET) could indicate filtering parameters or potential write side effects. The empty description significantly lowers confidence. Given the sibling tools context (CRUD tools for managing clients, sales, stock), this is most likely a read operation that uses POST for query parameters.

From the tool's own definition: "Tool name 'listar_tickets_post' suggests a listing/read operation ('listar' means 'list' in Portuguese), but uses POST method which could imply side effects; description is empty and uninformative."

## Use case

AI agents call listar_tickets_post to retrieve information from MCP Officegest without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "listar_tickets_post": {}
  }
}
```

## Other tools on MCP Officegest (305)

- `anular_recibo` — Destructive — https://policylayer.com/tools/rubencodex86-officegest-api-v2-mcp/anular-recibo.md
- `eliminar_documento_venda` — Destructive — https://policylayer.com/tools/rubencodex86-officegest-api-v2-mcp/eliminar-documento-venda.md
- `eliminar_draft` — Destructive — https://policylayer.com/tools/rubencodex86-officegest-api-v2-mcp/eliminar-draft.md
- `eliminar_fornecedor` — Destructive — https://policylayer.com/tools/rubencodex86-officegest-api-v2-mcp/eliminar-fornecedor.md
- `eliminar_job_falhado` — Destructive — https://policylayer.com/tools/rubencodex86-officegest-api-v2-mcp/eliminar-job-falhado.md
- `eliminar_marca` — Destructive — https://policylayer.com/tools/rubencodex86-officegest-api-v2-mcp/eliminar-marca.md
- `eliminar_modelo_etiqueta` — Destructive — https://policylayer.com/tools/rubencodex86-officegest-api-v2-mcp/eliminar-modelo-etiqueta.md
- `eliminar_proxy` — Destructive — https://policylayer.com/tools/rubencodex86-officegest-api-v2-mcp/eliminar-proxy.md
- `eliminar_sessao_profiler` — Destructive — https://policylayer.com/tools/rubencodex86-officegest-api-v2-mcp/eliminar-sessao-profiler.md
- `eliminar_sessoes_profiler` — Destructive — https://policylayer.com/tools/rubencodex86-officegest-api-v2-mcp/eliminar-sessoes-profiler.md
- `eliminar_unidade_medida` — Destructive — https://policylayer.com/tools/rubencodex86-officegest-api-v2-mcp/eliminar-unidade-medida.md
- `eliminar_vendedor` — Destructive — https://policylayer.com/tools/rubencodex86-officegest-api-v2-mcp/eliminar-vendedor.md
- `matar_job_queue` — Destructive — https://policylayer.com/tools/rubencodex86-officegest-api-v2-mcp/matar-job-queue.md
- `remover_linha_validacao` — Destructive — https://policylayer.com/tools/rubencodex86-officegest-api-v2-mcp/remover-linha-validacao.md
- `aceder_proxy` — Execute — https://policylayer.com/tools/rubencodex86-officegest-api-v2-mcp/aceder-proxy.md
- `aplicar_scaling` — Execute — https://policylayer.com/tools/rubencodex86-officegest-api-v2-mcp/aplicar-scaling.md
- `calcular_decisao_scaling` — Execute — https://policylayer.com/tools/rubencodex86-officegest-api-v2-mcp/calcular-decisao-scaling.md
- `comunicar_documento_at` — Execute — https://policylayer.com/tools/rubencodex86-officegest-api-v2-mcp/comunicar-documento-at.md
- `comunicar_documento_saft_ao` — Execute — https://policylayer.com/tools/rubencodex86-officegest-api-v2-mcp/comunicar-documento-saft-ao.md
- `comunicar_documentos_saft_ao` — Execute — https://policylayer.com/tools/rubencodex86-officegest-api-v2-mcp/comunicar-documentos-saft-ao.md
- `iniciar_sessao_profiler` — Execute — https://policylayer.com/tools/rubencodex86-officegest-api-v2-mcp/iniciar-sessao-profiler.md
- `parar_sessao_profiler` — Execute — https://policylayer.com/tools/rubencodex86-officegest-api-v2-mcp/parar-sessao-profiler.md
- `pausar_supervisor` — Execute — https://policylayer.com/tools/rubencodex86-officegest-api-v2-mcp/pausar-supervisor.md
- `reiniciar_supervisor` — Execute — https://policylayer.com/tools/rubencodex86-officegest-api-v2-mcp/reiniciar-supervisor.md
- `repetir_job_queue` — Execute — https://policylayer.com/tools/rubencodex86-officegest-api-v2-mcp/repetir-job-queue.md
- `repetir_submissao_saft_ao` — Execute — https://policylayer.com/tools/rubencodex86-officegest-api-v2-mcp/repetir-submissao-saft-ao.md
- `retomar_supervisor` — Execute — https://policylayer.com/tools/rubencodex86-officegest-api-v2-mcp/retomar-supervisor.md
- `sincronizar_tickets` — Execute — https://policylayer.com/tools/rubencodex86-officegest-api-v2-mcp/sincronizar-tickets.md
- `sincronizar_tickets_conta` — Execute — https://policylayer.com/tools/rubencodex86-officegest-api-v2-mcp/sincronizar-tickets-conta.md
- `comparar_sessoes_profiler` — Read — https://policylayer.com/tools/rubencodex86-officegest-api-v2-mcp/comparar-sessoes-profiler.md
- …and 275 more: https://policylayer.com/tools/rubencodex86-officegest-api-v2-mcp.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=rubencodex86-officegest-api-v2-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/rubencodex86-officegest-api-v2-mcp