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: r...
Part of the Project server.
Free to start. No card required.
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. PolicyLayer 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.
{
"version": "1",
"default": "deny",
"tools": {
"env_run_check": {
"limits": [
{
"counter": "env_run_check_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full Project policy for all 10 tools.
These attack patterns abuse exactly the kind of access env_run_check gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
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.
Register the Project MCP server in PolicyLayer and add a rule for env_run_check: 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 Project. Nothing to install.
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 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 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). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 10 Project 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.