List tickets for an employee with optional status filter.
AI agents call list_tickets to retrieve information from HR Assistant Agent 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 ticket information filtered by employee and optional status. It performs a read-only operation that does not create, modify, delete, or execute any actions. The blast radius of misuse is minimal—an agent could potentially view tickets it shouldn't have access to, but no data is changed and no external operations are triggered.
From the tool's definition Tool name 'list_tickets' and description 'List tickets for an employee with optional status filter' indicates retrieval of existing ticket data with no modification or side effects.
Attacks that exploit this kind of access
List tickets for an employee with optional status filter. It is categorised as a Read tool in the HR Assistant Agent MCP Server, which means it retrieves data without modifying state.
Register the HR Assistant Agent MCP server in PolicyLayer and add a rule for list_tickets: 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 HR Assistant Agent. Nothing to install.
list_tickets 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 list_tickets 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 list_tickets. 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.
list_tickets is provided by the HR Assistant Agent MCP server (nishu8875/hr-assistant-agent). 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 →