set_parameter
A write tool on the Revit MCP server.
This record as markdown: /tools/demolinator-revit-mcp-server/set-parameter.md
What set_parameter does on Revit MCP Server
AI agents use set_parameter to create or update resources in Revit MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Revit MCP Server environment.
Why set_parameter is rated Medium
The tool modifies data (Revit element parameters) reversibly, fitting the Write category. The lack of descriptive text lowers confidence slightly (0.85), but the clear naming pattern and context of sibling tools (create_detail_line, create_dimensions, etc.) confirm this is a model editing operation.
From the tool's definition Tool name 'set_parameter' indicates modification of parameters (properties) in Revit elements. No description provided, but naming convention strongly suggests reversible parameter modification.
Attacks that exploit this kind of access
The rule that runs set_parameter safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Revit MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set_parameter, this is the rule to start with:
set_parameter stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Revit MCP Server, apply this rule, and every set_parameter call is checked against it from then on.
Questions about set_parameter
set_parameter is a write tool on the Revit MCP Server MCP server. It is categorised as a Write tool in the Revit MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Revit MCP Server MCP server in PolicyLayer and add a rule for set_parameter: 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 Revit MCP Server. Nothing to install.
set_parameter is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_parameter 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 set_parameter. 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.
set_parameter is provided by the Revit MCP Server MCP server (demolinator/revit-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Revit MCP Server, and thousands of servers like it.
This server
Across the catalogue