Create page/route with routing setup
AI agents use create_page to create or update resources in MCP Software Engineer — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Software Engineer environment.
This tool creates new pages and routes in a web application. Creation of application pages is a Write operation—it modifies the codebase by adding new routes and pages, but these changes are reversible (pages can be deleted or modified). It does not execute arbitrary code (Execute), delete data (Destructive), or move money (Financial).
From the tool's definition Tool name 'create_page' and description 'Create page/route with routing setup' indicate creation of application routes and pages, which are reversible modifications to frontend/backend code structure.
Attacks that exploit this kind of access
Create page/route with routing setup. It is categorised as a Write tool in the MCP Software Engineer MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Software Engineer MCP server in PolicyLayer and add a rule for create_page: 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 MCP Software Engineer. Nothing to install.
create_page 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_page 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_page. 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_page is provided by the MCP Software Engineer MCP server (rajawatrajat/mcp-software-engineer). 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 →