Return datasource structure and validation information for creating valid datasources
AI agents call jasper_get_datasource_structure 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 retrieves and returns structural metadata about datasources (schema, validation rules, field definitions, etc.) to support datasource creation workflows. It performs no side effects, does not execute queries against datasources, and does not modify any resources. This is a straightforward read operation that queries configuration metadata.
From the tool's definition Tool name 'jasper_get_datasource_structure' and description 'Return datasource structure and validation information' indicate retrieval of metadata about datasource definitions without modification or execution of queries.
Documented attack patterns abuse exactly the kind of access jasper_get_datasource_structure 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_get_datasource_structure:
{
"version": "1",
"default": "deny",
"tools": {
"jasper_get_datasource_structure": {}
}
}jasper_get_datasource_structure 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.
Return datasource structure and validation information for creating valid datasources. 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_get_datasource_structure: 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_get_datasource_structure 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_get_datasource_structure 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_get_datasource_structure. 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_get_datasource_structure 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.