Perform comprehensive deep health check of all system components
AI agents call jasper_deep_health_check to retrieve information from Jasperreports without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
A health check is a read-only diagnostic operation that retrieves status information about system components. It performs no mutations, does not execute arbitrary code or commands, does not delete data, and does not involve financial transactions. While it may consume resources, it is fundamentally a monitoring/inspection tool that falls squarely within the Read category.
From the tool's definition Tool name 'jasper_deep_health_check' and description 'Perform comprehensive deep health check of all system components' indicate a diagnostic operation that queries system state without modifying or executing operations.
Documented attack patterns abuse exactly the kind of access jasper_deep_health_check gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Jasperreports, and nothing reaches the server without passing your rules. This is the rule we recommend for jasper_deep_health_check:
{
"version": "1",
"default": "deny",
"tools": {
"jasper_deep_health_check": {}
}
}jasper_deep_health_check 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.
Perform comprehensive deep health check of all system components. It is categorised as a Read tool in the Jasperreports MCP Server, which means it retrieves data without modifying state.
Register the Jasperreports MCP server in PolicyLayer and add a rule for jasper_deep_health_check: 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 Jasperreports. Nothing to install.
jasper_deep_health_check 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 jasper_deep_health_check 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 jasper_deep_health_check. 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.
jasper_deep_health_check is provided by the Jasperreports MCP server (mr-wolf-gb/jasperreports-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Jasperreports, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
37 Jasperreports tools catalogued and risk-classified — across an index of 43,000+ MCP servers.