AI agents call jasper_component_health 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.
This tool performs a health check—a read-only diagnostic operation that queries the state of a system component and returns status information. It has no side effects, does not modify data, does not execute arbitrary code, and does not delete or move resources. It is purely informational, similar to a status or monitoring query.
From the tool's definition Tool name 'jasper_component_health' and description 'Test health of a specific system component' indicate a diagnostic query that retrieves status information without modifying or executing operations.
Documented attack patterns abuse exactly the kind of access jasper_component_health 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_component_health:
{
"version": "1",
"default": "deny",
"tools": {
"jasper_component_health": {}
}
}jasper_component_health 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.
Test health of a specific system component. 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_component_health: 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_component_health 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_component_health 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_component_health. 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_component_health 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.