Get count of similar incidents for analytics
AI agents call get_similar_incidents 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 analytical metrics (incident counts) from the dashboard backend. It performs no data modification, deletion, code execution, or financial transactions. Consistent with sibling tools (get_ai_flags_distribution, get_dashboard_analytics, get_status_distribution, etc.), all of which are clearly read operations. Misuse by an AI agent would be limited to information disclosure, representing low risk.
From the tool's definition Tool name 'get_similar_incidents' and description 'Get count of similar incidents for analytics' indicate a retrieval operation that queries incident data for analytical purposes.
Attacks that exploit this kind of access
Get count of similar incidents for analytics. 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_similar_incidents: 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_similar_incidents 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_similar_incidents 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_similar_incidents. 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_similar_incidents 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 →