Get historical health data for trend analysis. Returns recent health check history including component status changes, resource usage trends, and system performance over time. Returns: Dictionary containing historical health information
AI agents call get_health_history to retrieve information from MaverickMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves system health and performance monitoring data without side effects. It queries historical information about component status, resource usage trends, and system performance—classic read-only operations. The context of a stock analysis MCP server suggests this is infrastructure/monitoring data retrieval rather than portfolio modification or financial transactions.
From the tool's definition Tool name 'get_health_history' and description 'Get historical health data for trend analysis' and 'Returns recent health check history' indicate data retrieval only. No modification, deletion, execution, or financial operations are described.
Documented attack patterns abuse exactly the kind of access get_health_history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MaverickMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_health_history:
{
"version": "1",
"default": "deny",
"tools": {
"get_health_history": {}
}
}get_health_history is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get historical health data for trend analysis. Returns recent health check history including component status changes, resource usage trends, and system performance over time. Returns: Dictionary containing historical health information. It is categorised as a Read tool in the MaverickMCP MCP Server, which means it retrieves data without modifying state.
Register the Maverick MCP server in PolicyLayer and add a rule for get_health_history: 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 MaverickMCP. Nothing to install.
get_health_history 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_health_history 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_health_history. 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_health_history is provided by the Maverick MCP server (wshobson/maverick-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 54 MaverickMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
54 MaverickMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.