Get full details of a ticket by ref (e.g.
AI agents call get_ticket_status to retrieve information from Vidal Helpdesk without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves existing ticket information by reference identifier. It performs a read-only operation that retrieves data without creating, modifying, deleting, or executing any changes. The low severity reflects minimal blast radius even if misused by an AI agent, as it only exposes existing ticket metadata without enabling any destructive or financial actions.
From the tool's definition Tool name 'get_ticket_status' and description 'Get full details of a ticket by ref' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get full details of a ticket by ref (e.g. It is categorised as a Read tool in the Vidal Helpdesk MCP Server, which means it retrieves data without modifying state.
Register the Vidal Helpdesk MCP server in PolicyLayer and add a rule for get_ticket_status: 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 Vidal Helpdesk. Nothing to install.
get_ticket_status 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_status 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_status. 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_status is provided by the Vidal Helpdesk MCP server (vidal-renao/vidal-helpdesk-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 →