Ejecuta type-check, lint o tests en el proyecto y devuelve el resultado. Usar antes de hacer commit o cuando el agente necesita verificar que los cambios no rompieron nada. Args: - check: qué verificación ejecutar - scope: ruta específica a verificar (opcional, ej: "src/app/dashboard") Retu...
Part of the Project MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke env_run_check to trigger processes or run actions in Project. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
env_run_check can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
env_run_check:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full Project policy for all 10 tools.
Agents calling execute-class tools like env_run_check have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
env_run_check is one of the high-risk operations in Project. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
Ejecuta type-check, lint o tests en el proyecto y devuelve el resultado. Usar antes de hacer commit o cuando el agente necesita verificar que los cambios no rompieron nada. Args: - check: qué verificación ejecutar - scope: ruta específica a verificar (opcional, ej: "src/app/dashboard") Returns: resultado del comando con errores y warnings.. It is categorised as a Execute tool in the Project MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for env_run_check. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Project MCP server.
env_run_check 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 env_run_check rule in your Intercept 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 Intercept policy for env_run_check. 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.
env_run_check is provided by the Project MCP server (project-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept