Retrieve tickets with optional filtering and pagination
AI agents call get_tickets to retrieve information from Respona Dashboard MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool fetches ticket data from the Respona Dashboard backend with optional filters and pagination controls. It has no side effects—it does not create, modify, delete, or execute operations. The blast radius of misuse is low since an agent could only access existing ticket information, not alter systems or cause financial harm. The tool belongs firmly in the Read category.
From the tool's definition Tool name 'get_tickets' and description 'Retrieve tickets with optional filtering and pagination' indicate a query operation that retrieves data without modifying or deleting anything.
Attacks that exploit this kind of access
Retrieve tickets with optional filtering and pagination. It is categorised as a Read tool in the Respona Dashboard MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Respona Dashboard MCP Server MCP server in PolicyLayer and add a rule for get_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 Respona Dashboard MCP Server. Nothing to install.
get_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 get_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 get_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.
get_tickets is provided by the Respona Dashboard MCP Server MCP server (raihan0824/mcp-respona-dashboard). 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 →