Read-only lookup for Movidesk ticket history, comments, inline comment images, statuses, and interactions. Rate limit: use one call at a time; avoid bulk history scans.
AI agents call get_ticket_history to retrieve information from Mcp Movidesk without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and queries existing ticket history data from the Movidesk API. It performs a passive read operation with no capacity to create, modify, delete, or execute external actions. The 'Read-only' designation in the description and the server context ('Read-only MCP server for querying') confirm this is a safe data retrieval operation.
From the tool's definition Tool name 'get_ticket_history' and description explicitly states 'Read-only lookup' with no modification capabilities.
Attacks that exploit this kind of access
Read-only lookup for Movidesk ticket history, comments, inline comment images, statuses, and interactions. Rate limit: use one call at a time; avoid bulk history scans. It is categorised as a Read tool in the Mcp Movidesk MCP Server, which means it retrieves data without modifying state.
Register the Mcp Movidesk MCP server in PolicyLayer and add a rule for get_ticket_history: 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 Movidesk. Nothing to install.
get_ticket_history 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 get_ticket_history 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 get_ticket_history. 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.
get_ticket_history is provided by the Mcp Movidesk MCP server (sandroscheuermann/mcp-movidesk). 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 →