Get ticket statistics and metrics
AI agents call get_ticket_stats 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 retrieves and queries aggregated ticket statistics and metrics from the Respona Dashboard backend without creating, modifying, deleting, or executing any operations. It has no side effects and poses minimal risk if misused by an AI agent—the worst outcome would be exposure of dashboard metrics already authorized for the user.
From the tool's definition Tool name 'get_ticket_stats' and description 'Get ticket statistics and metrics' indicate data retrieval only. All sibling tools are also query/read operations (get_*, distribution, stats, analytics patterns).
Attacks that exploit this kind of access
Get ticket statistics and metrics. 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_ticket_stats: 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_ticket_stats 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_stats 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_stats. 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_stats 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 →