jasper_health_status

THE RISK

Low Risk

Why jasper_health_status needs a policy

This tool retrieves monitoring/diagnostic information about system health status. It queries state without modifying, creating, deleting, or executing operations. The read-only nature and informational purpose make this a low-severity Read operation.

From the tool's definition Tool name contains 'health_status' and description states 'Get comprehensive health status' - a retrieval operation with no side effects. The verb 'Get' indicates data querying only.

Documented attack patterns abuse exactly the kind of access jasper_health_status gives an agent:

POLICY

How to control jasper_health_status

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_health_status:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "jasper_health_status": {}
  }
}

jasper_health_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Jasperreports — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Jasperreports tools

Destructive jasper_delete_job Delete a scheduled job Destructive jasper_delete_resource Delete a resource from JasperReports Server Execute jasper_cancel_execution Cancel a running asynchronous report execution Execute jasper_run_job_now Execute a scheduled job immediately Execute jasper_run_report_async Start asynchronous report execution and return execution ID for tracking Execute jasper_run_report_sync Execute a report synchronously and return the generated content Write jasper_create_job Create a scheduled report job Write jasper_create_role Create a new role

All 37 Jasperreports tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about jasper_health_status

What does the jasper_health_status tool do? +

Get comprehensive health status of the JasperReports MCP Server and connected systems. It is categorised as a Read tool in the Jasperreports MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on jasper_health_status? +

Register the Jasperreports MCP server in PolicyLayer and add a rule for jasper_health_status: 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.

What risk level is jasper_health_status? +

jasper_health_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit jasper_health_status? +

Yes. Add a rate_limit block to the jasper_health_status 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.

How do I block jasper_health_status completely? +

Set action: deny in the PolicyLayer policy for jasper_health_status. 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.

What MCP server provides jasper_health_status? +

jasper_health_status 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.

Enforce policy on every Jasperreports tool call.

Start from Jasperreports, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →