lctx_execute_file · Logica Context MCP: Risk & Policy

WHAT IT DOES

What lctx_execute_file does on Logica Context

AI agents invoke lctx_execute_file 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_file needs a policy

The tool executes code within a filesystem directory context, which can run arbitrary operations with side effects dependent on the code content and directory state. This is a classic Execute category risk—code execution whose outcomes depend on tool arguments (the file and its contents). While output is auto-indexed (a side effect), the primary function is code execution.

From the tool's definition Tool name contains 'execute' and description states 'running code in its directory context.' This directly indicates arbitrary code execution capability.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

lctx_execute_file Rate-limited

lctx_execute_file 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_file": {
      "limits": [
        {
          "counter": "lctx_execute_file_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_file

What does the lctx_execute_file tool do? +

Process a file by running code in its directory context. 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_file? +

Register the Logica Context MCP server in PolicyLayer and add a rule for lctx_execute_file: 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_file? +

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

Can I rate-limit lctx_execute_file? +

Yes. Add a rate_limit block to the lctx_execute_file 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_file completely? +

Set action: deny in the PolicyLayer policy for lctx_execute_file. 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_file? +

lctx_execute_file 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.