create_schedule
A write tool on the Revit MCP server.
This record as markdown: /tools/demolinator-revit-mcp-server/create-schedule.md
What create_schedule does on Revit MCP Server
AI agents use create_schedule 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 create_schedule is rated Medium
Based on the 'create_' prefix and the architectural context of other creation tools on this server, this appears to create a new schedule object in Revit, which modifies the model state reversibly. This is a Write operation rather than Execute because it creates a specific data structure (schedule) rather than running arbitrary code.
From the tool's definition Tool named 'create_schedule' with no description provided; however, in Revit context and given sibling tools like 'create_detail_line', 'create_dimensions', 'create_duct', 'create_grid', 'create_level', the 'create_*' pattern indicates object…
Attacks that exploit this kind of access
The rule that runs create_schedule 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 create_schedule, this is the rule to start with:
create_schedule 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 create_schedule call is checked against it from then on.
Questions about create_schedule
create_schedule 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 create_schedule: 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.
create_schedule 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 create_schedule 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 create_schedule. 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.
create_schedule 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