渲染 REST Controller(@RestController + Bean Validation)。
AI agents use codegen_render_controller to create or update resources in DBJavaGenix — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DBJavaGenix environment.
This tool generates (creates) source code for a REST Controller. It writes/creates new code artifacts but does not execute them, delete data, or involve financial transactions. The blast radius is medium — auto-generated controller code could introduce security misconfigurations if misused, but the action itself is a reversible write operation (code file creation).
From the tool's definition 渲染 REST Controller(@RestController + Bean Validation) — 'render' indicates code generation/creation of a REST Controller class with annotations
Documented attack patterns abuse exactly the kind of access codegen_render_controller gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and DBJavaGenix, and nothing reaches the server without passing your rules. This is the rule we recommend for codegen_render_controller:
{
"version": "1",
"default": "deny",
"tools": {
"codegen_render_controller": {
"limits": [
{
"counter": "codegen_render_controller_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}codegen_render_controller 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.
渲染 REST Controller(@RestController + Bean Validation)。. It is categorised as a Write tool in the DBJavaGenix MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the DBJavaGenix MCP server in PolicyLayer and add a rule for codegen_render_controller: 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 DBJavaGenix. Nothing to install.
codegen_render_controller 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 codegen_render_controller 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 codegen_render_controller. 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.
codegen_render_controller is provided by the DBJavaGenix MCP server (zhaoxingpeng/dbjavagenix). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 33 DBJavaGenix tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
33 DBJavaGenix tools catalogued and risk-classified — across an index of 42,500+ MCP servers.