lctx_execute · Logica Context MCP: Risk & Policy

WHAT IT DOES

What lctx_execute does on Logica Context

AI agents invoke lctx_execute to trigger actions in Logica Context. 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.

WHY IT NEEDS A POLICY

Why lctx_execute needs a policy

This tool runs arbitrary code across multiple languages (shell, python, node, ruby, php, go, swift, rust, deno) in a sandboxed environment. Although sandboxing provides some containment, the ability to execute shell commands and general-purpose code means an AI agent could perform unintended system operations, data exfiltration, or environmental modifications.

From the tool's definition Tool name contains 'execute' and description explicitly states 'Execute code in a sandboxed environment' with support for multiple languages including shell, which can trigger external operations and system commands.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

lctx_execute Rate-limited

lctx_execute stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "lctx_execute": {
      "limits": [
        {
          "counter": "lctx_execute_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Logica Context, so you can run agents against it safely.

FAQ

Questions about lctx_execute

What does the lctx_execute tool do? +

Execute code in a sandboxed environment. Supported languages: shell, node, python, ruby, php, go, swift, rust, deno. Output is auto-indexed. It is categorised as a Execute tool in the Logica Context MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on lctx_execute? +

Register the Logica Context MCP server in PolicyLayer and add a rule for lctx_execute: 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 Logica Context. Nothing to install.

What risk level is lctx_execute? +

lctx_execute is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit lctx_execute? +

Yes. Add a rate_limit block to the lctx_execute 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.

How do I block lctx_execute completely? +

Set action: deny in the PolicyLayer policy for lctx_execute. 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.

What MCP server provides lctx_execute? +

lctx_execute is provided by the Logica Context MCP server (rovemark/logica-context). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.