15 tools. 4 can modify or destroy data without limits.
4 write tools that can modify data. Rate limits recommended.
Last updated:
Free to start. No card required.
Full per-tool breakdown → Model it in the token calculator →
Write operations (configure_jdt_ls, java_open_file) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.
Execute tools (java_restart, java_start) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.
{
"configure_jdt_ls": {
"limits": [
{
"counter": "configure_jdt_ls_per_hour",
"window": "hour",
"max": 30,
"scope": "grant"
}
]
}
} Prevents bulk unintended modifications from agents caught in loops.
{
"find_references": {
"limits": [
{
"counter": "find_references_per_minute",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
} Controls API costs and prevents retry loops from exhausting upstream rate limits.
The Java Jdtls server has 2 write tools including configure_jdt_ls, java_open_file. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Java Jdtls.
15 tools across 3 categories: Execute, Read, Write. 11 are read-only. 4 can modify, create, or delete data.
Register the Java Jdtls MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.
Starter policies for each. Same risk classification, live on your fleet in minutes.
Deterministic rules across all 15 Java Jdtls tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.