AI agents call query_responses to retrieve information from Tickiti without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or searches response data across authorized tickets. It performs a read-only query operation with filters, returning results without creating, modifying, deleting, or executing external operations. The blast radius of misuse is limited to unauthorized information disclosure within the scope of queue-authorized tickets, which is typical for Read operations in a helpdesk context.
From the tool's definition Tool name 'query_responses' and description indicating it performs a 'Bulk-query' operation across tickets with filtering. The verb 'query' and the filtering semantics indicate data retrieval without modification.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Bulk-query responses across every queue-authorised ticket, filtered by. It is categorised as a Read tool in the Tickiti MCP Server, which means it retrieves data without modifying state.
Register the Tickiti MCP server in PolicyLayer and add a rule for query_responses: 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 Tickiti. Nothing to install.
query_responses 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 query_responses 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 query_responses. 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.
query_responses is provided by the Tickiti MCP server (tickiti/tickiti-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 →