system_run_lisp
A execute tool on the AutoCAD MCP Pro MCP server.
This record as markdown: /tools/u-c4n-autocad-mcp/system-run-lisp.md
What system_run_lisp does on AutoCAD MCP Pro
AI agents invoke system_run_lisp to trigger actions in AutoCAD MCP Pro. 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 system_run_lisp is rated High
This tool allows arbitrary AutoLISP code execution within the AutoCAD environment. AutoLISP has broad capabilities including file I/O, system command invocation, and unrestricted CAD manipulation. An AI agent with access to this tool could execute malicious code, modify production drawings without audit trails, delete entities, corrupt files, or trigger destructive CAD operations.
From the tool's definition Tool name 'system_run_lisp' indicates execution of AutoLISP code. AutoLISP is a programming language embedded in AutoCAD that can modify drawings, invoke COM operations, execute external commands, and interact with the file system.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs system_run_lisp safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AutoCAD MCP Pro, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For system_run_lisp, this is the rule to start with:
system_run_lisp 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.
The button opens the PolicyLayer dashboard: create your workspace, connect AutoCAD MCP Pro, apply this rule, and every system_run_lisp call is checked against it from then on.
Questions about system_run_lisp
system_run_lisp is a execute tool on the AutoCAD MCP Pro MCP server. It is categorised as a Execute tool in the AutoCAD MCP Pro MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the AutoCAD MCP Pro MCP server in PolicyLayer and add a rule for system_run_lisp: 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 AutoCAD MCP Pro. Nothing to install.
system_run_lisp 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 system_run_lisp 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 system_run_lisp. 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.
system_run_lisp is provided by the AutoCAD MCP Pro MCP server (u-c4n/autocad-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AutoCAD MCP Pro, and thousands of servers like it.
Across the catalogue