AI agents use rename_class to create or update resources in JADX-MCP-SERVER — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your JADX-MCP-SERVER environment.
Renaming a class is a reversible modification operation that changes code structure but does not delete data or execute external operations. It fits the Write category (creates or modifies data reversibly).
From the tool's definition Tool name is 'rename_class' with description 'Renames a specific class.' This modifies class metadata/structure in the decompiled codebase representation.
Documented attack patterns abuse exactly the kind of access rename_class gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and JADX-MCP-SERVER, and nothing reaches the server without passing your rules. This is the rule we recommend for rename_class:
{
"version": "1",
"default": "deny",
"tools": {
"rename_class": {
"limits": [
{
"counter": "rename_class_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}rename_class 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.
Renames a specific class. It is categorised as a Write tool in the JADX-MCP-SERVER MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the JADX-MCP-SERVER MCP server in PolicyLayer and add a rule for rename_class: 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 JADX-MCP-SERVER. Nothing to install.
rename_class 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 rename_class 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 rename_class. 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.
rename_class is provided by the JADX-MCP-SERVER MCP server (zinja-coder/jadx-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 32 JADX-MCP-SERVER tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
32 JADX-MCP-SERVER tools catalogued and risk-classified — across an index of 42,500+ MCP servers.