AI agents invoke jasper_run_job_now to trigger actions in Jasperreports. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes a pre-configured job immediately, which is an Execute action that can trigger external operations (report generation, data processing, system integrations). The actual effects depend on what the job does, making it an Execute rather than Write tool. It's not Destructive unless the job itself deletes data, and not Financial unless configured for financial operations.
From the tool's definition "Execute a scheduled job immediately" - directly triggers execution of a job whose effects depend on the job's configuration and data sources.
Documented attack patterns abuse exactly the kind of access jasper_run_job_now 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_run_job_now:
{
"version": "1",
"default": "deny",
"tools": {
"jasper_run_job_now": {
"limits": [
{
"counter": "jasper_run_job_now_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}jasper_run_job_now stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Execute a scheduled job immediately. It is categorised as a Execute tool in the Jasperreports MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Jasperreports MCP server in PolicyLayer and add a rule for jasper_run_job_now: 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_run_job_now is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the jasper_run_job_now 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_run_job_now. 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_run_job_now 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.