AI agents invoke execute_script to trigger actions in FreeCAD MCP Server. 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.
execute_script is a code execution tool that can run arbitrary Python or FreeCAD scripts against a live FreeCAD instance. This permits triggering external operations whose effects depend on arguments—from reading data to modifying documents or triggering CAD operations. The high confidence reflects the unambiguous semantics of 'execute_script', though the empty description prevents certainty about guardrails.
From the tool's definition Tool named 'execute_script' with no description provided. The name alone indicates execution of arbitrary scripts.
Documented attack patterns abuse exactly the kind of access execute_script gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and FreeCAD MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for execute_script:
{
"version": "1",
"default": "deny",
"tools": {
"execute_script": {
"limits": [
{
"counter": "execute_script_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}execute_script 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.
Free to start. No card required.
execute_script. It is categorised as a Execute tool in the FreeCAD MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the FreeCAD MCP Server MCP server in PolicyLayer and add a rule for execute_script: 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 FreeCAD MCP Server. Nothing to install.
execute_script 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 execute_script 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 execute_script. 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.
execute_script is provided by the FreeCAD MCP Server MCP server (theosib/freecad-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from FreeCAD MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
9 FreeCAD MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.