listar_tickets_post

A read tool on the MCP Officegest MCP server.

SERVERMCP Officegest SOURCErubencodex86/officegest-api-v2-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/rubencodex86-officegest-api-v2-mcp/listar-tickets-post.md

WHAT IT DOES

What listar_tickets_post does on MCP Officegest

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.

RISK

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

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs listar_tickets_post safely

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

listar_tickets_post Allowed

listar_tickets_post is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about listar_tickets_post

What does the listar_tickets_post tool do? +

listar_tickets_post is a read tool on the MCP Officegest MCP server. It is categorised as a Read tool in the MCP Officegest MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on listar_tickets_post? +

Register the MCP Officegest MCP server in PolicyLayer and add a rule for listar_tickets_post: 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 MCP Officegest. Nothing to install.

What risk level is listar_tickets_post? +

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

Can I rate-limit listar_tickets_post? +

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

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

listar_tickets_post is provided by the MCP Officegest MCP server (rubencodex86/officegest-api-v2-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on MCP Officegest, and thousands of servers like it.

This server

All 306 MCP Officegest tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →