Run ESLint-style static checks and return warnings plus suggested fixes.
AI agents invoke lint_javascript_code to trigger actions in MCP SAPUI5 Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes linting operations on JavaScript code. While linting itself is generally non-destructive (read-only analysis), ESLint engines execute code parsing and rule evaluation logic. The tool's effects depend on the code being analyzed—it could identify security issues, performance problems, or other code quality concerns.
From the tool's definition Tool runs ESLint-style static checks, which involves executing a linting engine against code. The description explicitly states it 'runs' checks and returns suggested fixes, indicating code execution.
Attacks that exploit this kind of access
Run ESLint-style static checks and return warnings plus suggested fixes. It is categorised as a Execute tool in the MCP SAPUI5 Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP SAPUI5 Server MCP server in PolicyLayer and add a rule for lint_javascript_code: 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 MCP SAPUI5 Server. Nothing to install.
lint_javascript_code is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the lint_javascript_code 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 lint_javascript_code. 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.
lint_javascript_code is provided by the MCP SAPUI5 Server MCP server (santiagosanmartinn/mcpui5server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →