listar_tickets_post
AI agents call listar_tickets_post to retrieve information from MCP Officegest without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
'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
listar_tickets_post. It is categorised as a Read tool in the MCP Officegest MCP Server, which means it retrieves data without modifying state.
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.
listar_tickets_post 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_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.
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.
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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →