Get full results for a completed analysis.
AI agents call analysis_results to retrieve information from Oncallhealth without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries analysis results that have already been completed. It does not create, modify, delete, or execute any operations—it merely returns data. The low severity reflects that exposure of burnout analysis metrics poses minimal blast radius compared to tools that could modify on-call schedules or execute external actions. This is a standard Read operation.
From the tool's definition Tool name 'analysis_results' with description 'Get full results for a completed analysis' indicates retrieval of data from a completed operation. Verb 'Get' and the read-only nature of fetching results confirm this is a query operation without side effects.
Attacks that exploit this kind of access
Get full results for a completed analysis. It is categorised as a Read tool in the Oncallhealth MCP Server, which means it retrieves data without modifying state.
Register the Oncallhealth MCP server in PolicyLayer and add a rule for analysis_results: 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 Oncallhealth. Nothing to install.
analysis_results 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 analysis_results 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 analysis_results. 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.
analysis_results is provided by the Oncallhealth MCP server (rootly-ai-labs/mcp-on-call-health). 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 →