Refresh design table data from SQL source
AI agents invoke design_table_refresh to trigger actions in Solidworks. 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.
Refreshing from a SQL source executes an external data retrieval and update operation. It is not a pure read (it modifies the design table state) nor purely destructive, but it triggers an external SQL operation whose effects depend on the source data. This falls under Execute as it runs an external operation to update internal state.
From the tool's definition 'Refresh design table data from SQL source' - triggers an external operation (SQL query/data fetch) that updates the design table
Attacks that exploit this kind of access
Refresh design table data from SQL source. It is categorised as a Execute tool in the Solidworks MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Solidworks MCP server in PolicyLayer and add a rule for design_table_refresh: 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 Solidworks. Nothing to install.
design_table_refresh 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 design_table_refresh 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 design_table_refresh. 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.
design_table_refresh is provided by the Solidworks MCP server (solidworks-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →