AI agents use jasper_create_role to create or update resources in Jasperreports — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Jasperreports environment.
Creating a role modifies system state and can have security implications (roles define permissions and access controls), but the operation is reversible (roles can be deleted). This is a write operation rather than execute or destructive. Severity is high because improper role creation could grant unintended permissions, and the blast radius depends on how the created role is subsequently used and assigned to users.
From the tool's definition Tool named 'jasper_create_role' with description 'Create a new role'. The verb 'create' indicates a write operation that modifies the authorization model by adding a new role.
Documented attack patterns abuse exactly the kind of access jasper_create_role 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_create_role:
{
"version": "1",
"default": "deny",
"tools": {
"jasper_create_role": {
"limits": [
{
"counter": "jasper_create_role_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}jasper_create_role stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a new role. It is categorised as a Write tool in the Jasperreports MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Jasperreports MCP server in PolicyLayer and add a rule for jasper_create_role: 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_create_role is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the jasper_create_role 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_create_role. 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_create_role 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.